Summary | |||||||
testID | method | code | time(ms) | status | warn | error | DOM |
---|---|---|---|---|---|---|---|
dynamideToken | GET | 200 | 3 | SUCCESS |
SUCCESS: dynamideToken seq: 123 |
GET http://localhost:28080/tagonomy?mock=token&group=fooGroup2 |
200 gotExpected: true time: 3ms |
msg: OK |
alerts: |
resp-headers: Content-type: application/json Content-length: 204 Date: Tue, 08 Dec 2015 23:18:30 GMT |
vars: SELFTEST_PORT: 28080 GLOBALMASTERVAR1: global_mastervar_value_1 GLOBALMASTERVAR2: global_mastervar_value_2 SELFTEST_SERVER: http://localhost:28080 |
Summary | |||||||
SUCCESS | |||||||
EXPECTED | |||||||
FAILURE |
preflight is for expressions like loop="${['a','b']}" which get evaluated before the test gets created, so you'll see the same testID is shown with a new header in the eval report after the preflight section.
resource-found |
resource-cached |
resource-not-found |