Getting Started
Details
Integration
Introduction to Integration in Avo Assure
Integration with external tools is done in two ways; either with the Avo Assure API or inbuilt integration with Avo Assure. For all the integration using Avo Assure API, the below three steps need to be followed.
- 1.Token Generation
- 2.Export of Mindmaps Data
- 3.Execution of JSON
Token Generation
- 1.Log in as an admin user and navigate to the Tokens section.
Token Generation – Step 1
2. Select the ICE type for which the token has to be generated.
3. Select the user for which the token has to be generated. Fill in the following details:
- Token name
- Token expiry date and time
Token Generation – Step 2
4. On click of ‘Generate’, the token will be created.
Export of Mindmaps Data
- 1.Log in to Avo Assure as an end-user with access to Mindmaps.
- 2.Navigate to Mindmaps. Select the Module from the Assign Module page. For more information, refer here.
- 3.Select ‘Custom’ from the 'Export Mindmap to' options, and then click on the ‘Export’ button. Execution-related Module information is exported as a JSON file.
Exporting Module Information from Mindmaps
Execution JSON
- 1.Module Information has the test suite and test Scenario details that are to be executed.
Module Information File
1
{
2
"batchInfo": [{
3
"testsuiteName": "Dummy_Test",
4
"testsuiteId": "5ef4728c4f1df4328436833b",
5
"versionNumber": 0,
6
"appType": "Web",
7
"domainName": "Manufacturing",
8
"projectName": "Web",
9
"projectId": "5de4e4aed9cdd57f4061bca5",
10
"releaseId": "R1",
11
"cycleName": "C1",
12
"cycleId": "5de4e4aed9cdd57f4061c354",
13
"suiteDetails": [{
14
"condition": 0,
15
"dataparam": [" "],
16
"scenarioId": "5ef471d44f1df43284368333",
17
"scenarioName": "Dummy_Test"
18
}]
19
}]
20
}
Copied!
2. Execution template is divided into two parts: Execution Data and User Info.
3. Copy Module Info data extracted in the previous section into the Execution Template.
4. In the User Info section of Execution Template, fill the details of Generated Token hash, Token name, ICE name, and Pool name.
5. Multi-user execution is also supported, i.e. Executions for multiple users can also be triggered in one request. To achieve that, combine different execution request data in one list.
Multi-User Execution Request Data
1
{
2
"executionData": [{
3
"source": "api",
4
"executionMode": "serial",
5
"executionEnv": "default",
6
"browserType": ["1"],
7
"integration"{
8
"alm": {...},
9
"qtest": {...},
10
"zephyr": {...}
11
},
12
"batchInfo": [{...}],
13
"userInfo": {...}
14
}, {
15
"source": "api",
16
"executionMode": "serial",
17
"executionEnv": "default",
18
"browserType": ["1"],
19
"integration": {
20
"alm": {...},
21
"qtest": {...},
22
"zephyr": {...}
23
},
24
"batchInfo": [{...}],
25
"userInfo": {...}
26
}
27
.
28
.
29
.
30
{
31
"source": "api",
32
"executionMode": "serial",
33
"execcutionEnv": "default",
34
"browserType": ["1"],
35
"integration": {
36
"alm": {...},
37
"qtest": {...},
38
"zephyr": {...}
39
},
40
"batchInfo": [{...}],
41
"userInfo": {...}
42
}]
43
}
Copied!
Last modified 7mo ago
Copy link