Test Scenario Migration
The Test scenario migration wizard locates all test scenarios that have previously been executed (must have a .context file) and analyses all component metadata in the test scenarios against the component metadata in the repository for the environment specified in the .context file. Using the wizard makes it much easier to migrate test scenarios when a program interface changes.
An analyzed file can have one of the following states
- OK: All components conform to the repository definitions
- DIFF_DESCRIPTION: All components conform to the repository definitions but one or more definitions have descriptive values that are different. Its not necessary to migrate
- DIFF_METADATA: At least one component does not conform to the repository definition. Migration is required
- MULTIPLE_COMPONENTS: More than one component with the same name exists for the environment. It cannot be determined if the test scenario conforms to the repository values
- NO_CONTEXT: A test scenario was found but no .context file was found. Therefore the repository values cannot be found as it is unknown which environment to use.
- NO_COMPONENT: No component definition was found in the repository for the environment
- PARSE_ERROR: The test scenario cannot be parsed
Files with one of the DIFF_ states can be migrated automatically and the wizard can show suggested changes to the metadata as well as data before it is migrated.
Let us look at an example. In the screenshot below we have a folder with test scenarios where fields have been added or removed, one with major changes to the structure, one that cannot parse, one where only descriptions are different, one without any differences, and one where there are two components with the same name for the same environment and where the user has not chosen for the context which one to use.
Complete the following steps to migrate a folder like the preceding one.
Right-click on a parent folder and select
BMC AMI DevX Total Test
> Migrate Total Test Scenarios to open the migration wizard. This will open the migration wizard and list all found files. In the below screen shot we can see the files, their status, environment and a description of the problem.
- Three files were found to have differences in meta data. These have automatically been selected. One has a difference in description, one has no context file, one is OK, one has a parse error and one has multiple components.
- Select one of the files with DIFF_METADATA status and the differences are shown in the bottom of the wizard. The Metadata tab shows the metadata differences, here we see that a field char16 and a packed6 has been added to the linkage section and it shows the updated meta data to the right.
- At the Test data tab, concrete data from the test scenario is shown to the left and the suggested changes based on the new metadata to the right. Here we see that the char16 and packed6 fields have been added while the original values of the other fields are preserved.
- Click the Migrate selected button, and this will update the files and trigger a new analysis of the files. The updated list is now displayed.
- The rest of the files must be handled manually as these involve parse errors, no context file and multiple component definitions.