-
Notifications
You must be signed in to change notification settings - Fork 379
Create smoketests.yml #11070
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
Create smoketests.yml #11070
Conversation
Create yml that will run e2e smoke tests after PR comment has been edited (e.g. by Vercel update). The current tests is a simple initial test. i.e. Login and test app-trader account switcher.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
A production App ID was automatically generated for this PR. (log)
Click here to copy & paste above information.
|
🚨 Lighthouse report for the changes in this PR:
Lighthouse ran with https://deriv-app-git-markodonnell-deriv-create-e2etest-yml.binary.sx/ |
on question that I have is that on each comment edit action it's gonna run? |
@ali-hosseini-deriv |
Good question. I was just following the lighthouse yml model. If there's a better way of tiggering the run only after the Vercel site is ready, both processes would benefit. |
Co-authored-by: Ali(Ako) Hosseini <ali.hosseini@deriv.com>
Kudos, SonarCloud Quality Gate passed! |
Create yml that will run e2e smoke tests after PR comment has been edited (e.g. by Vercel update). This yml is based on the smoketest.yml that is already up and running in Deriv-com, with which @balakrishna-deriv has had some visibility.
The current test that this will run is a very simple. i.e. Login and test app-trader account switcher. We will add to the tests gradually so as to bed the process in gently.
NB. I have run this past @ali-hosseini-deriv and see https://app.clickup.com/t/20696747/FEQ-873, if other approvers require further info. And I have added the requisite E2E_ secrets as defined in the Cypress env variable section.
Changes:
Please provide a summary of the change.
Screenshots:
Please provide some screenshots of the change.