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

End-to-End tests for fullstack examples #3059

Open
ruheni opened this issue Aug 9, 2021 · 5 comments · May be fixed by #3447
Open

End-to-End tests for fullstack examples #3059

ruheni opened this issue Aug 9, 2021 · 5 comments · May be fixed by #3447
Labels
kind/improvement An improvement to existing feature and code.

Comments

@ruheni
Copy link
Contributor

ruheni commented Aug 9, 2021

Add end-to-end tests using Playwright, preferably for fullstack examples.

This would boost our confidence in the applications.

@ruheni ruheni added the kind/improvement An improvement to existing feature and code. label Aug 9, 2021
@pshaddel
Copy link

Hi @ruheni
I would like to help solve this issue for some of the examples. What is your opinion about using Cypress?

@ruheni
Copy link
Contributor Author

ruheni commented Aug 10, 2021

Hey @pshaddel,

That's awesome! I would prefer Playwright because it doesn't require any configuration to run

@pshaddel
Copy link

OK,
I will start working on first full stack example. Wish me luck with my first contribution in Prisma world :)

@pshaddel
Copy link

Thanks for the heads up. I took a look at the documentation of playwright. I think we are going to use @playwright/test and we are not going to use third parties like jest or jasmine.

@ruheni
Copy link
Contributor Author

ruheni commented Aug 10, 2021

That's correct. It'll be just a single file with groups of tests 🙂

@ruheni ruheni linked a pull request Jan 3, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/improvement An improvement to existing feature and code.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants