This change represents a bit of a paradigm shift in the test strategy. Previously we had intended to have a single test driver and multiple test suites in order to cover the matrix of needed tests.
Now the design is to have multiple tests drivers and a single test suite. This way its clear that all tests (with rare exceptions) run against both kind of infrastructure. The tests themselves are decoupled from the kind of infrastructure they target.
The two kinds of infrastructure are:
Hermetic - isolated infrastructure
Durable - real world public infrastructure
See the README for more details.
Closes WS1-1262
Closes WS1-1264
WIP TODO:
[x] The test driver does not yet ensure we are using update to date clients.
[x] ~Decide on name of driver binary (right now it uses the longest name, I am thinking we use the short name hermetic)~ Using hermetic-driver
This change represents a bit of a paradigm shift in the test strategy. Previously we had intended to have a single test driver and multiple test suites in order to cover the matrix of needed tests.
Now the design is to have multiple tests drivers and a single test suite. This way its clear that all tests (with rare exceptions) run against both kind of infrastructure. The tests themselves are decoupled from the kind of infrastructure they target.
The two kinds of infrastructure are:
Hermetic - isolated infrastructure Durable - real world public infrastructure
See the README for more details.
Closes WS1-1262 Closes WS1-1264
WIP TODO:
hermetic)~ Usinghermetic-driver