Considering merging together the `tasty` and `hspec` test drivers
Historically speaking the tests I wrote for the DB operations were written with the intent of being run sequentially, in case we wanted to rely on the results of a previous test in the next one. Given that requirement, I wanted only those kind of tests to be run sequentially, and given that tasty
doesn't support per-test-group sequential running, I had to split the test suite in two parts, one using tasty
as the driver and one using hspec
as the driver.
However, we later changed things such that our database tests can run in parallel, which means that in principle the use of two test drivers is unnecessary and sometimes confusing.
I would like to use tasty-hspec
to run our existing hspec tests using a single driver, and remove the need for garg-test-hspec
. I think that having a single testsuite stanza will help setting up things like hpc
if we want to run any kind of test coverage analysis on the codebase.