Skip to content
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

Update to use codecept.io #62

Closed
Nighthawk14 opened this issue Jul 20, 2016 · 4 comments
Closed

Update to use codecept.io #62

Nighthawk14 opened this issue Jul 20, 2016 · 4 comments

Comments

@Nighthawk14
Copy link
Contributor

Protractor 4.0.0 has been released and contains some good features. As well it now has typings for typescript. 👍

@uglow
Copy link
Contributor

uglow commented Jul 22, 2016

Maybe this issue could be changed to use codecept.io once it is stable. Thoughts?

@Nighthawk14
Copy link
Contributor Author

Definitely 👍. I'm waiting for the PR to be merged codeceptjs/CodeceptJS#167

@uglow uglow changed the title Update protractor to 4.0.0 Update to use codecept.io Jul 28, 2016
@Nighthawk14
Copy link
Contributor Author

Some feedback on this, I would still suggest to upgrade protractor to 4.0.10 now, codecept is an interesting tool but we found some annoying things after using it here :), it's mostly bugs but that means it's not quite ready yet.

@uglow
Copy link
Contributor

uglow commented Nov 9, 2016

Thanks @Nighthawk14 . Can you elaborate on the bugs you found, please?
I'm quite fond of the idea of being able to write tests that target the DOM, not the framework that creates the DOM. While Protractor DOES work with non-Angular sites, Codecept hides this from the test-writer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants