Appearance
HP ALM Json file Migration
Preconditions
JRE/JDK version
The machine (PC, Mac, or virtual machine) where you run the migration tool must have JRE or JDK version 21 or later installed.
TestOps version
WARNING
MIGRATION AVAILABLE FOR TESTOPS VERSION > 4.26.0
Configuration file example
- Export your ALM test cases as json in format:
json
{
"tests": [
{
"id" : "123",
"name" : "Test name",
"description" : "Some description",
"severety" : "High",
"path" : [
"Folder name 1",
"Folder name 2",
"Folder name 3"
],
"steps" : [
{
"name": "Step 1",
"action" : "<html><body>Some action 1</body></html>",
"expected" : "<html><body>Some expected 1</body></html>"
},
{
"name": "Step 2",
"action" : "<html><body>Some action 2</body></html>",
"expected" : "<html><body>Some expected 2</body></html>"
},
...
]
}
]
}- use this example to configure migration
Configuration file example
Create the json file with content like:
json
{
"type": "alm-json",
"debug": true,
"oneByOne": false,
"allureConfig": {
"endpoint": "https://demo.testops.cloud/",
"token": "1f4b4acd-418c-4d0b-8533-1d747abb7599",
"projectId": 173,
"migrationTagPrefix": "alm",
"folderCfPrefix": "Folder"
},
"almJsonConfig": {
"path": "/path/to/file/exampletest",
"attachmentsPath": "/path/to/attachments",
"withAttachmentsNamesInSteps": true
}
}Configuration parameters
| Name | Mandatory | Description | Example |
|---|---|---|---|
| commonProperties | yes | see description here: Common properties | |
| allureConfig | yes | see description here: Allure TestOps properties | |
| almJsonConfig.path | yes | Absolute path to JSON file with ALM export | |
| almJsonConfig.attachmentsPath | yes | Absolute path to the folder with ALM attachments Use file name pattern for attachments: ALM__<almId>STEP<stepNumber>_<name> Where: - <almId> = ALM testcase ID - <stepNumber> = step number; use “0” for case attachment - <name> = attachment name | |
| almJsonConfig.withAttachmentsNamesInSteps | no | If this flag is true, there will be attachment names in the scenario like: Step #1: Some action [attach:<attachment_name>] with attachment ` | - <attachment_name>` |