-
Notifications
You must be signed in to change notification settings - Fork 115
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
recording ui-session-id for report portal logging #13055
Conversation
trigger: test-robottelo |
413ad54
to
0f49790
Compare
trigger: test-robottelo |
0f49790
to
2fa8683
Compare
trigger: test-robottelo |
2fa8683
to
044acd1
Compare
trigger: test-robottelo |
trigger: test-robottelo |
044acd1
to
ae4534d
Compare
ae4534d
to
45f151a
Compare
trigger: test-robottelo |
trigger: test-robottelo |
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 Great!
BTW I would incline towards creating pytest plugin out of it rather than having conftest file with same contents at each sub-directory (like ui, destructor you are doing). In plugin you can choose to filter the path for the tests and then record the property for ui session.
With this pytest plugin, we can open it in future for everyone.
For now, I'm moving this to the |
* recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check (cherry picked from commit 3e4abae)
* recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check (cherry picked from commit 3e4abae)
* recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check (cherry picked from commit 3e4abae)
recording ui-session-id for report portal logging (#13055) * recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check (cherry picked from commit 3e4abae) Co-authored-by: Omkar Khatavkar <[email protected]>
recording ui-session-id for report portal logging (#13055) * recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check (cherry picked from commit 3e4abae) Co-authored-by: Omkar Khatavkar <[email protected]>
recording ui-session-id for report portal logging (#13055) * recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check (cherry picked from commit 3e4abae) Co-authored-by: Omkar Khatavkar <[email protected]>
* recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check
recording ui-session-id for report portal logging (#13055) * recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check
* recording ui-session-id for report portal logging * moving the fixture to common location and adding fspath check
Problem Statement
Currently, We are unable to retrieve the Selenium UI session ID from the Airgun GitHub repository and integrate it into our automation testing tool, Robottelo. This session ID is crucial because during the test recording process, videos are generated by the Selenium Airgun repository, and these videos are associated with specific UI session IDs. To improve our testing workflow and enhance the usability of our test results, we need to establish a mechanism that allows us to access this session ID within Robottelo and incorporate it into the JUnit XML results. By doing so, we can leverage the power of the Report Portal logging system, enabling other team members to easily locate and access the video links associated with each test result for comprehensive test result review.
Solution
Airgun PR
SatelliteQE/airgun#1038