Add support for `fail fast` option
See original GitHub issueHi GoogleChrome team!
I was wondering if a fail fast option, same as we see in testing library like jest
, could be implemented on Lighthouse CI?
My use case is pretty simple: I want to run lighthouse twice on all my HTML pages, but when the same assertion fail on each pages, the CI result is quite overloaded… making it difficult to read and fix with ease.
Having such an option could prevent lighthouse from running further on pages that will encounter similar assertion issue.
Thanks a lot for your feedback 😉
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
`--fail-fast` option - Command line - RSpec Core - Relish
Use the --fail-fast option to tell RSpec to stop running the test suite on the first failed test. You may add a parameter...
Read more >How To Fail Faster -- And Why You Should - Forbes
We need to encourage others to fail fast and safely. Then we need to glean lessons learned and disseminate the learning throughout the...
Read more >Fail Fast Testing - GitLab Docs
Fail fast testing is useful when adding new functionality to a project and adding new automated tests. Your project could have hundreds of...
Read more >Fail Fast and Fail Safe Iterators in Java - GeeksforGeeks
Fail -fast iterators checks the modCount flag whenever it gets the next value (i.e. using next() method), and if it finds that the...
Read more >Fail Fast - Martin Fowler
A system that fails fast does exactly the op- ... won't fail fast without my help, so I assert that ... adding assertions...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You can accomplish this yourself today by running
lhci collect --numberOfRuns=1
, running your assertions withlhci assert
, and then runninglhci collect --numberOfRuns=N-1 --additive
before uploading.It’s potentially feasible to introduce such a mode via a flag to
autorun
but we’re currently focused on features for LHCI that enable solutions to unsolved problems.Hi @patrickhulce,
Thanks again for your answer. Sounds like a great argument and I completely understand your position.
I am closing the issue, feel free to reopen if more people ask for this feature to be implemented.
Have a nice day! 😎 🤖