-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
What is current Playwright test coverage? #7051
Comments
@yangwao i can start with the ones that are simpler, some others are complex and I'll take some to to study/re implement them |
ASSIGNED - @prury 🔒 LOCKED -> Thursday, August 31st 2023, 18:34:34 UTC -> 24 hours |
ASSIGNMENT EXPIRED - @prury has been unassigned. |
@nick-dev123 please lmk if you are going to refactor another one so we can split the load |
So currently, there are 24 tests? Seems we don't cover inputs well |
Yes, and I'm already coding some new ones as we speak, expect a PR from me this week
Change price modal got introduced recently, and to test anything that requires signing a transaction needs something different than just a mockaddress to interact with koda. I have been studying the subject tho, talked with some ppl in the last few days. I'm separating tests by their page/relation, instead of testing all the possible inputs in one test. Usually my workflow is as follows: Check test list priority(example):
then i think about test cases for a specific page/component Transfer Page:
As you can observe, there are many test related work fronts lmk what you think of it |
@prury Which tests are you working on from the list? |
Transfer and Landing so far, also adding some small fixtures, let me improve this list, just a moment |
@nick-dev123 done, this list will suffer changes as we go, but that's it for now! lmk which one you want! |
some work, some don't, i am aware and i have been trying to fix them for nuxt in the last few days, but will need a bit more of time |
Duplicate of #7826 |
I think we should have test coverage for current functionality before we switch to Nuxt3
This is currently we had with Cypress?
Current playwright tests
Probably we should extended them at least on level we've had with Cypress
Originally posted by @yangwao in #6920 (comment)
The text was updated successfully, but these errors were encountered: