-
-
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
fix the #6167 - F key misleading message #6182
Conversation
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 up 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 the corporate CLA signed. If you have received this in error or have any questions, please contact us at [email protected]. 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! |
Codecov Report
@@ Coverage Diff @@
## master #6182 +/- ##
==========================================
+ Coverage 64.19% 64.32% +0.13%
==========================================
Files 219 219
Lines 8423 8423
Branches 3 4 +1
==========================================
+ Hits 5407 5418 +11
+ Misses 3015 3004 -11
Partials 1 1
Continue to review full report at Codecov.
|
Does this fix the case reported in #6167? While I think this message is clearer, it's unclear to me how it would fix the bug? |
As far as I understood and verified the bug is actually about displaying a wrong information, the behavior is correct. |
Oh, that's a very good point. It's just confusing that the message is the same 🙂 |
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. |
Summary
Fixes #6167
Changed the
"Press
f
to run all tests. " to "Press f to quit "only failed tests" mode" when inside only failed tests mode.Test plan
Scenario is covered by the "shows the correct usage for the f key in "only failed tests" mode".
Also:
And