Appends results to a specific asynchronous test session...
Syntax
Basic syntax
Test("Basic syntax", Test.APPEND( testName ), function() {
// If the test called "testName" is running, any results from this
// test will be added to "testName"
});
Parameters
Parameter
Type
Mandatory
Notes
API Version
testName
String
The name of the test to append results to.
If that test is not currently active, invocations of the Test.APPEND( ) will be ignored.
1.0
Return values
Value
Type
Notes
API Version
<mode>
Object
The mode object is associated with the unit test defined in the same Test() invocation.
1.0
<error>
Error
If a testName is not specified, or a test with that name is not currently queued or running, an error will be thrown.
1.0
Effect on test
A Test.APPEND( ) Unit Tests redirects its results to the initiating test in an asynchronous session if that session is currently active.
The Test.APPEND( ) test is effectively treated as if it were part of the initiating Test.ASYNCH( ) test:
Only the initiating Test.ASYNCH( ) unit test will have a pass/fail state
Test.APPEND( ) unit tests merely contribute towards the Test.ASYNCH( ) unit test's pass/fail state
similarTo( ) — A deep similarity checking assertion...
notSimilarTo( ) — A deep dissimilarity spotting assertion...
Test Signals — Signals are used to prematurely terminate Unit Tests...
REQUIRE( ) — Check whether a test or group of tests have passed. If the requirement fails, a RequireSignal will be sent which terminates the current test and marks it as failed.
ABORT( ) — Aborts the current test, marking it as failed in the process...
FINISH( ) — Terminates the test as if it had finished normally...