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

Add Acceptance Tests #18

Closed
tomatau opened this issue Feb 24, 2016 · 1 comment · Fixed by #296
Closed

Add Acceptance Tests #18

tomatau opened this issue Feb 24, 2016 · 1 comment · Fixed by #296

Comments

@tomatau
Copy link
Owner

tomatau commented Feb 24, 2016

Need to figure out a good solution for acceptance tests.. once one is down, a full 'Acceptance' Journey can be coded up and integrated.

Requirements

  • can run any browser (possible browserstack or something?)
  • can integrate easily with circleCI
  • can run a complete user journey or more
  • debuggable
  • (nice to have) can mock out API calls
  • open source
  • friendly API for handling transitions or animations, navigating, page events and powerful selectors

Braindump

  • Not something in ruby, php, java or any other lang (we're a JS only project here!)
  • Not dalek - seems unstable, although good
  • Not intern - don't want gulp/grunt.. already using mocha only for functional and unit tests
  • Maybe buster - I haven't researched it
  • Maybe nightwatch - good but doesn't support babel needs extra helpers for consistent assertions
  • Maybe cypresIO - good but doesn't support babel, also Early access beta... can mock API calls which is very powerful but maybe not needed for a full journey anyway as we have functional tests.
  • Not just selenium, casper is helpful here but could be much more work... same with webdriver io
  • Not pioneer, seems very similar to nightwatch but less popular
  • Not protractor, avoiding karma and it's more about angular
@tomatau
Copy link
Owner Author

tomatau commented Nov 5, 2018

Going with cypress as it is more deterministic and supports more browsers now. Only issue is it doesn't support safari because of safari reasons but that's acceptable. Chrome and Edge should be enough to get an idea of app behaviour in browsers.

Working on docker images and strategy to manage all this in a clean and happy way.

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

Successfully merging a pull request may close this issue.

1 participant