-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add some tests for JS components #2469
Comments
I think we should have less frontend code to maintain, meaning we can do browser testing 💯. I have so little experience with Playwright. I did some scrapers and automation tools but nothing related to testing yet 🤔. I believe we need this to prevent such regressions 🫡. |
I haven't done much playwright either - I'm defo quite keen to have a play 👀 |
I have a toy package called OpenAPIPages and I think it needs some browser-based testing 🚀. I'll search for other packages that does browser-based testing to get inspired by. Let me know if you know/find any please 😇. |
We have a bunch of functionality that is in JavaScript, but nothing that really tests that side of the project. To prevent regressions, such as we've just seen with #2468, we should add some test coverage here.
This could either be direct JS tests, or something like Playwright that can do functional (browser) testing.
The text was updated successfully, but these errors were encountered: