-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testcafe 3.0 support #133
Comments
Hi @kojoru, Not to worry, I'll start working on it right away. I admit I haven't checked on TestCafe's versions for a while now. It's usually a pretty straightforward process, so if we are lucky you can even expect a new release tonight (well it really depends on your timezone but you get the idea) Edit: serves me right, not as easy as usual |
Okay, so it looks like there a few breaking changes, nothing I can't work out though. HOWEVER, there is also an issue which seems to come from TC3 itself, I'd say a bug on their side or in one of their dependencies. IMHO it would be better to wait for TC version 3.0.1 before upgrading, the current version is pretty new and I usually wait for a week or two before attempting the update. However if you're really confident you can work around the issue or you really need some new feature, I'll publish it despite my lack of confidence (probably as a rc version) EDIT: the new version 3.0.1 is more stable, but basic http authentication still doesn't work. I tested it with vanilla testcafe so the issue doesn't come from this package. |
it seems DevExpress/testcafe#7852 is fixed now, is it was a blocker? |
No changes were need on the runner side so any version previously supported should still be supported now #133
No changes were need on the runner side so any version previously supported should still be supported now #133
It was not really a blocking issue, but earlier versions of TC3 were not stable enough to my taste. |
Hi,
Can I ask you to investigate v3 support for Testcafe?
Is there anything we can do to facilitate peer dependencies upgrade from our side? I would be happy to assist, if so.
The text was updated successfully, but these errors were encountered: