-
Notifications
You must be signed in to change notification settings - Fork 5
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
[FEATURE] End to End testing #243
Comments
tombeckenham
added a commit
that referenced
this issue
Dec 10, 2024
- Added Playwright test dependencies to package.json and pnpm-lock.yaml. - Updated .gitignore to exclude test results and Playwright reports. Closes #243
tombeckenham
added a commit
that referenced
this issue
Dec 11, 2024
- Updated ESLint configuration to include e2e tests. - Changed Playwright test directory from './tests' to './e2e'. - Adjusted TypeScript configuration to include e2e files. - Removed obsolete test files: example.spec.ts and wallet.spec.ts. Closes #243
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue to be solved
There are no automated tests on the extension. This makes it difficult for engineers to know if they have broken anything when developing or merging a feature. It also slows down the process of QA.
Suggest A Solution
Implement basic end to end testing using Playwright (which is the only solution that supports chrome extension testing). Support the standard set of tests from the test template to start with. As we find bugs or implement new features, add tests to cover those cases.
The text was updated successfully, but these errors were encountered: