...
| Code Block |
|---|
module.exports = defineConfig({
env: {
"aioTests": {
"enableReporting": true,
"cloud": { //Replace with server authentication if using Jira Server
"apiKey": "apikey for cloud"
},
"jiraProjectId": "NVTES",
"cycleDetails": {
"createNewCycle": true,
"cycleName": "Cypress first run from plugin",
"cycleKey": "NVTES-CY-2",
"folder": ["Cloud","Smoke Test Nightly"],
"tasks": ["NVTES-1","NVTES-2]
},
"addNewRun": true,
"addAttachmentToFailedCases": true,
"createNewRunForRetries": true,
"addTestBodyToComments": true
},
},
e2e: {...
}} |
Configurable values
Value | Description |
|---|---|
enableReporting | Set to true to make the current run update results to AIO Tests. Default false. |
jiraProjectId | Jira Project key to update results to |
cycleDetails.createNewCycle | Set to true to create a new cycle for run being reported |
cycleDetails.cycleName | Works if createNewCycle is true, sets the cycle name of cycle getting created |
cycleDetails.cycleKey | AIO Tests cycle key that should be updated. Used if createNewCycle is false |
cycleDetails.folder | Folder hierarchy, where first item in array is parent folder and so on eg.["Parent","Child"] |
cycleDetails.tasks | List of Jira Issue Keys to attach as Tasks to created cycle, impacts only when creating new cycle |
addNewRun | Create a new run or update an existing run in the cycle |
addAttachmentToFailedCases | Set to true to attach screenshots, if available, for failed cases |
createNewRunForRetries | Set to true if each retry should create a new run |
addTestBodyToComments | Set to true test script body should be added as a comment in a failed case |
Logging
AIO Tests Reporter logs can be seen in the run logs as below for successful updates
...
For any queries, suggestions or issues, please feel free to reach out @ help@aioreportsmailto:help@aiotests.com