TESTING ZEETIX

These links may be used to run tests on Zeetix services. This is a placeholder that is expected to be replaced by an interactive test runner.

Several of these links take minutes to run. The JSON output is more legible when run in a current (v114.0.2) Firefox browser instance. The "JSON Viewer" (v2.0.0) Chrome extension provides the same viewer in the Chrome browser. These links work best on a desktop (as opposed to phone) browser. Each answers a JSON-encoded result object with the following top-level structure:

{
    _clazzName: "TestResult"
    _passed: [], // List of TestCase instances that pass
    _errors: [], // List of TestCase instances that have errors
    _failures: [], // List of TestCase instances that fail
}

Each passing test item has the following structure:

{
    _clazzName: "GateCorpusEndpointsTest",  // The name of a TestCase descendant
    _testSelector: "testCleanup",           // The name of the test
    _phases: "11111111",                    // Binary digit string
    _errors: [],                            // Always empty for passing test
}

A successful test run has no errors and no failures.

Each TestCase in TestResult (whether passed, error, or failed) has a phases string. This is binary digit string. Each digit ("0" or "1") reports a phase of the test case execution. A value of "1" means that the phase succeeded, and a value of "0" means that the phase failed. A "passed" test case has a value of all-ones ("11111111").

  1. isTestCaseStarted: Execution began
  2. isSetUpStarted: The "setUp" phase started
  3. isSetUpDone: The "setUp" phase finished
  4. isPerformTestStarted: The "performTest" phase started
  5. isPerformTestDone: The "performTest" phase finished
  6. isTearDownStarted: The "tearDown" phase started
  7. isTearDownDone: The "tearDown" phase finished
  8. isTestCaseDone: Execution finished.

A test that throws an unexpected exception during execution is an error. A single test may report more than one error. Each error occurs in one of eight (8) test phases. A "0" in the phases field allows the error to be localized to a specific phase. Each item in the list of errors has the following structure:

{
    _clazzName: "GatePipelineTest",         // The name of a TestCase descendant
    _testSelector: "testMultipleSetCorpus", // The name of the test
    _errorDescription: {
        message: "Runtime error",           // The message of the exception
        details: "Not a Boolean argument"   // The details of the exception
        stack: "..."                        // (elided) The stack trace of the exception
    },
    _phases: "11110111",                    // Each "0" is a test phase with an error
    _errors: [
        {
            name: "ErrorException",
            description: '{"message":"Runtime error","details":"Not a Boolean argument"}',
        }

    ],
}

In the above error entry, a "0" is in digit 5 of phases. This means that the "performTest" phase started and did not finish. The final three "1" digits show that the test harness successfully performed the "tearDown" phase and gracefully finished after the error.

The stack, together with phases, usually identifies the specific code where the unexpected exception was thrown. The value of stack is often very long and is elided here for clarity.