-
Notifications
You must be signed in to change notification settings - Fork 393
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
Adding different viewports to e2e testing #1321
Comments
Yes, totally agree with that. Add viewports for: |
For this ticket, the goal is to make sure that we are running all e2e tests at different viewports. If tests fail: create bug or update e2e test. Future: what new e2e tests should be created that are specific to mobile? |
PR #1615 |
GH-1321) (#1615) * fix bugs and added new viewports * fixed conflict * fixed filter problem * removed another timeout in e2e * forgot to uncomment a line when I was testing locally * improvements * added changes with Kate * added other mobile versions for safety * added fix to big happy path * added changes to places where classes changed * finalized again, and I am 99% it is done * test push to run the build again * reverted the test to make it run again: * chnaged mobile name too * changed the old data set in e2e assertion to the new on in the server * changed hardcoded url pointing to electronics to spa requests * added fix for shipping tabs / test passes in dev-17-source-of-truth * fixed unit test * removed fdescribe in the unit test...
Our e2e tests only tests the desktop version of our application, but we do not know if it works perfectly for different viewports. Therefore, it would be best to include 'mobile' versions in order to not miss any bugs or errors.
Nightly builds (or at will), because essentially we're running the tests 6 times.
Update DoD as well.
The text was updated successfully, but these errors were encountered: