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.

Sign up for GitHub

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

Jump to bottom

Configure UI test automation #3

Closed
malparty opened this issue Jun 2, 2021 · 2 comments
Closed

Configure UI test automation #3

malparty opened this issue Jun 2, 2021 · 2 comments
Assignees
@malparty
Labels
Chore !ci-cd Work made on task automations for integration & deployment @0.1.0 Initial release
Milestone
0.1.0

Comments

@malparty
Copy link
Owner

malparty commented Jun 2, 2021 •
edited
Loading

Why?

Save time with automation and enforce quality checks by:

  • Enable UI test execution via GitHub Actions on PR creation/updates.
  • Enforce UI tests before PR validation/merge.

Who Benefits?

Development team
@malparty malparty added @0.1.0 Initial release !ci-cd Work made on task automations for integration & deployment labels Jun 2, 2021
@malparty malparty added this to the Environment & project initial setup milestone Jun 2, 2021
@malparty malparty self-assigned this Jun 2, 2021
@malparty malparty added the Chore label Jun 3, 2021
@malparty malparty modified the milestones: Environment & project initial setup, 0.10 Jun 7, 2021
@malparty malparty mentioned this issue Jun 8, 2021
Merged
malparty added a commit that referenced this issue Jun 8, 2021
@malparty
[#3] Create sample UI test in order to validate system test auto exec…
64d2716 
…ution
@malparty
Copy link
Owner Author

malparty commented Jun 8, 2021

@ankitkalia1195 @junan after some tests (and learning/hands-on), the initial config is already working, no need to change any line of code.
So I will pass this issue as "Ready for QA" without using the step "In Code Review".
Feel free to tell me if such practice is not ok -- and eventually how to handle such case in a better way ;-)
Thanks!

@junan
Copy link
Contributor

junan commented Jun 9, 2021

@malparty As it is already working with the initial config. So I think there is no need for "In Code Review" in this case as there are no changes in the code.

@malparty malparty mentioned this issue Jun 11, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@malparty malparty

Labels
Chore !ci-cd Work made on task automations for integration & deployment @0.1.0 Initial release
Projects
None yet
Milestone
0.1.0
Development

No branches or pull requests
2 participants
@junan @malparty