git-test
git-test copied to clipboard
mhagger
Run automated tests against a range of Git commits and keep track of the results
Document the existing `GIT_TEST_VERBOSITY` and add two new `GIT_TEST_NAME` plus `GIT_TEST_PREVIOUS_CHECKED_OUT_COMMIT`. I think the last one should be able to solve issue #13. Not automatically out of the box like...
- `list`: output nothing if there are no tests - `remove`: don’t raise an exception if there is no `default` to remove
On 21048cca949f (“Merge pull request #19 from mhagger/iter-tests”, 2021-05-03). ``` $ # Remove only test $ ~/git-test/bin/git-test remove $ ~/git-test/bin/git-test list Traceback (most recent call last): File "/home/kristoffer/git-test/bin/git-test", line 1129,...
A command may leave the working tree dirty (e.g. the command is applying code formatters to the tree). In such a case, we should stop running tests and allow the...
As mentioned in issue #11, the `forget-results` command's default behaviour of deleting everything will be super dangerous if it ever gains support for deleting individual results. I have now added...
To make `git-test` usable in my repositories, I have to add `git submodule update --init --force --recursive` to the top of my build script. It seems that this should be...
It took me a while to work out how to get git-test to forget the results for a single commit, despite it being in the README, because I was expecting...
Currently it's only possible to run a single test at a time, at least without multiple invocations of git-test. It'd be useful to me to be able to specify multiple...
It seems like the main utility of this over a `rebase -x` method (besides the result caching) is to run it asynchronously. I wonder how hard it would be to...
Support running multiple tests per commit. e.g. `git test run -t build,lint,unittest main..mybranch`
These are changes I have been using locally for a long time, and would like to have applied upstream. It resolves the majority of issue #12. Commit *"Add support for...