Summary | |||||||
testID | method | code | time(ms) | status | warn | error | DOM |
---|---|---|---|---|---|---|---|
importer | GET | 200 | 3 | SUCCESS |
SUCCESS: importer seq: 117 |
GET http://localhost:28080/tagonomy?mock=true&TOKEN_ID=success |
200 gotExpected: true time: 3ms |
msg: OK |
alerts: |
req-headers: : 1.0|idm|idm|piid=ffffffff540e662de4b01ef1c4c50faf&sessid=401d6f4ee6bb4795af0861ebaa1f6c58|2014-11-05T01:01:16+00:00|2014-11-05T04:01:16+00:00|cbc0b7e17f07a90f70a88a0eab57d9ce |
resp-headers: Content-type: application/json Content-length: 67 Location: http://localhost:18080/tagonomy?mock=true Date: Tue, 08 Dec 2015 23:18:30 GMT |
location: http://localhost:18080/tagonomy?mock=true |
vars: SELFTEST_PORT: 28080 GLOBALMASTERVAR1: global_mastervar_value_1 GLOBALMASTERVAR2: global_mastervar_value_2 TOKEN_ID: success |
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 |