Page History
...
Code Block | ||
---|---|---|
| ||
{ "tests" : [ { "testKey" : "DEMO-57", "start" : "2014-08-30T12:19:23+01:00", "finish" : "2014-08-30T12:20:01+01:00", "comment" : "Error executing step 2!", "status" : "FAILED", "steps": [ { "status": "PASSED", "actualResult": "Step 1: OK" }, { "status": "FAILED", "actualResult": "Step 2 *Failed* with an unexpected error message", "evidences" : [ { "data": "(... base 64 encoded ...)", "filename": "screenshot1.jpg", "contentType": "image/jpeg" } ] } ] } ] } |
Example 4: Importing test results with Test Run Custom Fields
This is a simple example of a JSON file with execution results with Test Run Custom Fields values.
Code Block | ||
---|---|---|
| ||
{
"info": {
"summary": "Execution of automated tests for release v1.3",
"description": "This execution is automatically created when importing execution results from an external source",
"user": "admin",
"startDate": "2014-08-30T11:47:35+01:00",
"finishDate": "2014-08-30T11:53:00+01:00"
},
"tests": [
{
"testKey": "DEMO-25",
"start": "2014-08-30T11:47:35+01:00",
"finish": "2014-08-30T11:50:56+01:00",
"comment": "Successful execution",
"status": "FAIL",
"customFields": [
{
"id": 1,
"value": "true"
},
{
"id": 2,
"value": "13400"
},
{
"id": 3,
"value": "Test instance is refreshed"
}
]
}
]
} |
Example 5: Importing data-driven manual test results with auto-provisioning of tests
This is an example of a JSON file with a single test result.
...