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

Feeding report back for focusing on failed test-cases #1386

Open
koct9i opened this issue Apr 10, 2024 · 1 comment
Open

Feeding report back for focusing on failed test-cases #1386

koct9i opened this issue Apr 10, 2024 · 1 comment

Comments

@koct9i
Copy link

koct9i commented Apr 10, 2024

It would be nice to have built-in option for feeding json-report back into loop and use it as natural data source for focusing on failed test-cases. (Probably it's already there but I don't see anything similar)

Unlike to "go test" caching this will work explicitly for the end user.

Generally, there's a lot useful features which could be implemented in testing suites if core framework could provide standard way to fetch previous results.

@onsi
Copy link
Owner

onsi commented Apr 15, 2024

hey sorry for the delay - I've been out of pocket for a few weeks. This is a great idea and one that's popped into my head a few times - but not something I've ever prioritized or built.

There are certainly some edge cases (e.g. what if the test suite changes and you try running with an old report) and connecting a spec in the report with a spec in the suite is surprisingly non-trivial (there are no truly unique identifiers - you have to do it on the basis of a combination of file line/number and test text.

But this would be a great addition. The v0 for this could be something like --focus-failures=report.json which would just rerun failures. If you're interested in working on this I could point out at the places in the code, documentation, and test suites where the necessary changes would need to occur. I think it'll be a relatively straightforward change modulo those edge cases above.

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

No branches or pull requests

2 participants