Add end to end tests using Cypress test runner #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I have noticed that the project lacks any tests and took liberty to write a few using Cypress.io test runner. The tests are exercising all methods, except for
find(because there are 2 arguments, not one like other tests). Each test grabs the code from the input, evaluates it and compares to the shown output. Here is example of the test runner going through tests when opened withnpm run test:guiThe test runner in action in this video https://youtu.be/6-nI6lW3zM0
Two new script commands
npm run test:guito open Cypress GUI and see the tests locally.npm testto run Cypress without GUI (good for CI)Both assume the app is running at
http://localhost:8080