-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
feat: interactive failure runs #10858
feat: interactive failure runs #10858
Conversation
Hi @NullDivision! Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
4c970a9
to
4ae9184
Compare
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
4 similar comments
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
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.
This looks pretty good! Could you add a gif to the OP that shows how it looks in use?
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.
thanks! left some nits, code lgtm 👍
4a22ccf
to
d6aad96
Compare
Question: why is this a separate plugin from the interactive snapshot one? Wouldn't it make sense for this to be 1 plugin? Possibly with some "sub-mode" for "just tests" or "just snapshots" |
I've actually thought about that myself and for the most part it would be a fairly straightforward solution but would also mean refactoring some stuff:
The choice was either to copy the logic as is and refactor at a later date or risk breaking something in the existing plugin. For an initial implementation I thought it might make more sense to do the former. But I'm open (albeit somewhat reluctant) to doing the refactor in this PR) |
@thymikee @jeysal @rickhanlonii thoughts? |
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.
I'm good with this being a separate plugin, but if we want to refactor, make it in a separate PR. Also, how about combining 2 tests into one for FailedTestInteractive, is it feasible?
I'm not sure I follow. Are you talking about combining the test instrumentation and usage info tests? Can do. |
@NullDivision yes, thanks! |
d6aad96
to
486efd7
Compare
486efd7
to
816d298
Compare
feat: add plugin logic
Apply suggestions from code review Co-authored-by: Simen Bekkhus <sbekkhus91@gmail.com> style: update usage info labels test: merge tests with similar conditions
816d298
to
d853b70
Compare
Thanks @NullDivision! |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Closes #7685.
Summary
When running multiple failed tests we may end up with a lot of noise in tests (console logs, deprecation warnings, etc.). Using an interactive mode would allow us to run and fix each test in isolation without having to manually run and re-run tests.
Test plan