Headless testing (resolves #204) #292
Merged
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
…ents to run server from within playwright
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.
This branch adds some browser-based testing (using Playwright) — at the moment, this is only configured to work in the GitHub CI environment (since I didn't want to have to add unnecessary
package.jsonfiles to the repository). But it can be run locally using:npm i @playwright/test @node/types --no-save npx playwright install --with-deps chromium npx playwright test --config ./ci/playwright.config.js // Runs on 8080At the moment, this just confirms that the tests pass successfully (e.g. the final test div is created with a
success completeclass). But we could definitely add more tests (including checking popState, results scrolling, or ensuring that different UI components like the autocomplete all work successfully)