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.

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

Add Espresso video recording to CI [Blocked: #1831] #1832

Open
BenHenning opened this issue Sep 9, 2020 · 0 comments
Open

Add Espresso video recording to CI [Blocked: #1831] #1832

BenHenning opened this issue Sep 9, 2020 · 0 comments
Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

Is your feature request related to a problem? Please describe.
Understanding why an Espresso test fails will be difficult just looking at the failure reason in CI (since most will be along the lines of "failed to perform UI action on element X").

Describe the solution you'd like
One way to significantly ease the debuggability of Espresso tests running in CI is to record a video of the test & upload it as an artifact (for both cases when the test is failing and passing). The recording helps authors investigate failed tests, and helps reviewers understand the changes for passing tests.

Describe alternatives you've considered
This is proposing a specific solution (video recording), so alternatives aren't specifically desirable. We could consider uploading screenshots or relying on screenshot tests for most situations, but this is more general-purpose and could actually aid in developing/investigating screenshot tests.

Additional context
#1831 needs to be completed first (actually having Espresso tests running in CI).

@BenHenning BenHenning added Type: Improvement Priority: Nice-to-have This work item is nice to have for its milestone. labels Sep 9, 2020
@Broppia Broppia added issue_type_feature Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 29, 2022
@BenHenning BenHenning added Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. issue_type_infrastructure Z-ibt Temporary label for Ben to keep track of issues he's triaged. and removed mini-project labels Sep 14, 2022
@seanlip seanlip added bug End user-perceivable behaviors which are not desirable. and removed issue_type_infrastructure labels Mar 28, 2023
@MohitGupta121 MohitGupta121 added the Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. label Jun 16, 2023
@seanlip seanlip removed the bug End user-perceivable behaviors which are not desirable. label Jun 16, 2023
@seanlip seanlip added enhancement End user-perceivable enhancements. and removed Type: Improvement labels Jun 16, 2023
@seanlip seanlip removed the Priority: Nice-to-have This work item is nice to have for its milestone. label Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Development

Successfully merging a pull request may close this issue.

4 participants