-
Notifications
You must be signed in to change notification settings - Fork 25
chore: critical flow html reporting - WPB-22537 #4050
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
Conversation
Test Results16 tests 16 ✅ 6m 49s ⏱️ Results for commit f68a456. ♻️ This comment has been updated with latest results. Summary: workflow run #21430121078 |
|
netbe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, made a suggestion but maybe we discuss it as a separate point
netbe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM;)
(cherry picked from commit ab6c8d8)
(cherry picked from commit ab6c8d8)
Summary
Briefly describe about this PR changes.
A new yaml for allure reporting has been created and added as publish report and report summary to critical_flows.yaml.In pipeline Allure html report generation job is added sequentially after the test run. Whilerunning workflow manually after execution of run tests it generates allure report from *.xcresults with screenshot/video for failure cases.
This is how execution flow now looks:

Testing
Describe how to verify the changes locally. Attach screenshots of local execution if relevant.
ref PR: https://github.com/wireapp/wire-ios/actions/runs/20464908307To view the report, scroll down the run to look for allure report something like this:

this creates a single html file while can be opened to any browser and view the report.
this is how actual report looks like:

Additional Information
any more info, add here.