Mathew Attlee

Using detection would be my preferred approach though I am wondering 🤔 how to test it with specs on CI unless there is a way to temporarily override the cargo...

> CI fails because the runner doesn't have nextest installed, what do I do? Let me have a think about this and get back to you

I think the solution is to temporarily override `cargo` so that it behaves how we want it to in terms of the exit code https://advancedweb.hu/how-to-mock-in-bash-tests/

What happens if you open one of the fixture folders for the jest or mocha specs and try running vim-test?

Do you mean this? https://jenkins.io/doc/pipeline/tour/tests-and-artifacts/

If you have time could create a pull request with an example of your situation in the fixtures and specs and I'll happily implement the logic for it.

Yeah I saw but I need concrete examples of how it should behave for each thing like TestNearest, TestFile and what CLI commands it should generate as that would make...

I wonder if the PR #328 may provider a solution to this

This is a very good question, which strategy are you using currently? Off the top of my head custom strategies might be what you're looking for

Not sure how to best approach this situation. What are your thoughts @janko?