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
{{ message }}
This repository has been archived by the owner on Oct 4, 2023. It is now read-only.
We are currently in the process of validating the Yaks README with Ataru. One issue we run in into is that we have a long list of failures, and minitest puts them in a random order.
This is very annoying when you're trying to fix things, because you pick a single example that you're trying to fix, but each time you run Ataru it shows up somewhere else in the output.
This use case could be addressed in two ways. If we could stop the output from being randomized, then one could simply work on the current first or last example. Or if you could tell ataru to only check a single example, you could just focus on that until it works.
Are either of these possible right now? Would it be easy to add?
We are currently in the process of validating the Yaks README with Ataru. One issue we run in into is that we have a long list of failures, and minitest puts them in a random order.
This is very annoying when you're trying to fix things, because you pick a single example that you're trying to fix, but each time you run Ataru it shows up somewhere else in the output.
This use case could be addressed in two ways. If we could stop the output from being randomized, then one could simply work on the current first or last example. Or if you could tell ataru to only check a single example, you could just focus on that until it works.
Are either of these possible right now? Would it be easy to add?
/cc @mifix
The text was updated successfully, but these errors were encountered: