Skip to content
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

Implement basic testing strategy for Swyxkit #63

Open
swyxio opened this issue May 16, 2022 · 2 comments
Open

Implement basic testing strategy for Swyxkit #63

swyxio opened this issue May 16, 2022 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@swyxio
Copy link
Owner

swyxio commented May 16, 2022

We copied over the default Playwright tests in #62

But they are super naive. perhaps we should test the navigation and the search?

help?

@swyxio swyxio added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels May 16, 2022
@taismassaro
Copy link
Contributor

hey @sw-yx, I'm not familiar with Playwright, so I'd like to give this a try if it's still up for grabs :)

@swyxio
Copy link
Owner Author

swyxio commented Oct 6, 2022

yes @taismassaro up for grabs! also you can talk to @debs-obrien if you need playwright help!

one problem i have right now: the blog pages are rendered serverlessly, so it is possible for the build to succeed but for the pages to fail to render at runtime. how might an E2E test catch this issue?

(playwright probably cannot catch my specific problem, which is a netlify build issue, but just giving ideas for how to E2E test a blog with search/clientside navigation/rendering functionality)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants