-
Notifications
You must be signed in to change notification settings - Fork 35
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
Cypress e2e testing #280
Cypress e2e testing #280
Conversation
local testing npm run compile
npm run build:prod
npm run cy:open |
I added a simple test for #275 we can add more tests on the fly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice feature! I just tested it and it works like charm.
@sgratzl How should we proceed with this PR? Should I wait for further implementation or merge it once you addressed my two minor change requests?
Notes from my test run:
I installed the npm dependencies in my Linux subsystem for Windows (WSL1) and ran npm run cy:open
. I waited for a few minutes and then cancled the verification step.
> cypress open
It looks like this is your first time using Cypress: 4.3.0
⠋ Verifying Cypress can run /home/user/.cache/Cypress/4.3.0/Cypress
As alternative I downloaded the Cypress Desktop and loaded the LineUp repository there. Then everything worked like it should be and all tests are green.
merge then we can start using it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good!
closes #227 depends on #279
prerequisites:
Summary
wip of using cypress to run e2e tests.
Notes
/build/src
Local testing
Variant 1: with prebuilt LineUp
Variant 2: with webpack-dev-server
First shell:
Second shell: