Re:Ava – Simple concurrent test runner
by geoelectric on Friday August 28, 2015 @01:11PM
(#10136658)
Test automation professional here.
"Hermetic" means not relying on the performance of resources not under test, such as an external server. You get away from that with a combo of test doubles, fake servers, or real servers running on test localhost/cluster and strictly under that machine's control.
"Atomic" isn't really a standard term in testing as much as "hermetic" is (though I haven't heard "hermetic" much either until recently when Google Testing Blog started popularizing it).
Edit: googling "atomic unit test" shows that it's used more widely than I thought.
But generally, just by what "atomic" means (stands alone), I would interpret that to mean not sharing state between tests--i.e. nothing where the last test creates your fixture and your next test uses it, or multiple tests together form a sequenced scenario.
Re:Ava – Simple concurrent test runner
by andrewmcwatters on Friday August 28, 2015 @12:18PM
(#10136290)
What does Sindre Sorhus actually make besides those two iPhone apps he put on the app store? He's a widely seen name in JS open source, but if you only write tiny bits of software here and there to help other people write software, are you really making anything, or just making the process a bigger pain?
Creating "yet another javascript framework" isn't really progressing the industry in any way.
We normally call this "hermetic", not "atomic".
"Hermetic" means not relying on the performance of resources not under test, such as an external server. You get away from that with a combo of test doubles, fake servers, or real servers running on test localhost/cluster and strictly under that machine's control.
"Atomic" isn't really a standard term in testing as much as "hermetic" is (though I haven't heard "hermetic" much either until recently when Google Testing Blog started popularizing it).
Edit: googling "atomic unit test" shows that it's used more widely than I thought.
But generally, just by what "atomic" means (stands alone), I would interpret that to mean not sharing state between tests--i.e. nothing where the last test creates your fixture and your next test uses it, or multiple tests together form a sequenced scenario.
QUnit uses it that way too, for example:
https://qunitjs.com/cookbook/#keeping-tests-atomic
Of course, your group might normally call that "hermetic," but you'd be out of step with most others.