You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn't find an option or an issue/PR for this, so apologies if this has already been requested!
It could be handy to have a limit on the maximum number of specs run. I mainly run into this when switching branches that are way out of date with the main branch - it'll end up running a ton of specs because a ton of files were changed, and it might take ~15-20 minutes to run all the specs and might tax my CPU. It might be nice to be able to say, if more than 10 files change, or more than 10 spec files would be re-run, don't do anything. For me, guard-rspec is most helpful for doing TDD, so I prefer it for the quick feedback on stuff I'm editing rather than getting all the specs re-run after a branch change.
Thanks!
The text was updated successfully, but these errors were encountered:
ibrahima
changed the title
Feature request: Limit maxium number of specs run
Feature request: Limit maximum number of specs run
Jul 30, 2021
I couldn't find an option or an issue/PR for this, so apologies if this has already been requested!
It could be handy to have a limit on the maximum number of specs run. I mainly run into this when switching branches that are way out of date with the main branch - it'll end up running a ton of specs because a ton of files were changed, and it might take ~15-20 minutes to run all the specs and might tax my CPU. It might be nice to be able to say, if more than 10 files change, or more than 10 spec files would be re-run, don't do anything. For me, guard-rspec is most helpful for doing TDD, so I prefer it for the quick feedback on stuff I'm editing rather than getting all the specs re-run after a branch change.
Thanks!
The text was updated successfully, but these errors were encountered: