Support Forum
Hm.. So `t.exit()` has to throw the exception - no other way to interrupt the test. I'll revert that.
Read the API documentation
Thank you for the patience. Reverted to always throw the exception and improved `waitFor` handling. Please verify the new behavior in the tomorrow nightly.
Read the API documentation
You are welcome! We are planning 5.5.0 release in a week or two (it is stable already and nightly is pretty much the same).
Read the API documentation
Sorry to bother you again but I found way to break your breakTestOnFail config.
When the test fails due to an exception within the tested code the next subtest is launched. Change 'Subtest 2' to:
When you run the given example, 'Subtest 3' is executed.
When the test fails due to an exception within the tested code the next subtest is launched. Change 'Subtest 2' to:
st.it('Subtest 2', function(sst) {
sst.chain(function(next) {
sst.is(2, 2);
sst.foo(); // sst.foo is not a function
sst.waitForElementVisible('foo', next);
}, function(next) {
sst.waitForElementVisible('foo', next);
sst.is(3, 3);
});
});