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

Scope to failures #227

Merged
merged 4 commits into from
Oct 6, 2024
Merged

Scope to failures #227

merged 4 commits into from
Oct 6, 2024

Conversation

Canop
Copy link
Owner

@Canop Canop commented Oct 5, 2024

In short

If you ran a test job, and there's a failure, hit f to have the job "scoped" to the failures, ie not executing other tests.

If you want to go back to all tests, hit esc.

Fix #214

Details

cargo test doesn't support passing several test keys, so scoping only takes the first failure.

If you're running another test command, for example cargo nextest run, then all failures are part of the scope.

It's possible to start bacon in scoped mode: bacon test(mymodule::some_fun). Hitting esc will bring you to the unscoped tests.

If you want to define a different binding (maybe you're already using the f key), you can refer to the scope-to-failures internal. For example:

[keybindings]
alt-f = "scope-to-failures"

@Canop Canop merged commit ae7e675 into main Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a command to relaunch tests but limited to the failing one(s)
1 participant