During development I won't care about a lot of tests, especially integration tests (which are often slow(er)). By using tags I could declare sets of unit tests I care about and are likely to break because of what I'm working on.
This would make it more convenient to run tests frequently.
Running all tests is more appropriate for checkin hooks and CI.
This feature could be combined with #6, #7, #14
Examples:
It should be supported to add tags at group and test level, where tags on a group apply also to tests within that group.
I just found an example where this is already done http://olivinelabs.com/busted/.
During development I won't care about a lot of tests, especially integration tests (which are often slow(er)). By using tags I could declare sets of unit tests I care about and are likely to break because of what I'm working on.
This would make it more convenient to run tests frequently.
Running all tests is more appropriate for checkin hooks and CI.
This feature could be combined with #6, #7, #14
Examples:
server)server,unittest) (as don't runintegrationtests)firefox)-skip) (excludeskip)authentication)It should be supported to add tags at group and test level, where tags on a group apply also to tests within that group.
I just found an example where this is already done http://olivinelabs.com/busted/.