FanfareSVT and iTest have similar but not identical types offiles. During the migration process, anew iTest workspace is created and assets from FanfareSVT are copied/convertedinto their iTest equivalients. I willbriefly describe how SVT files relate to their iTest counterparts.
Test Case
SVT and iTest both have extremely similar test case files.During migration, there is a one for one relationship between files. Indices for steps will change during theimport process since steps for conditional logic get "nested" and there are no"end" steps.
A for loop in SVT, had a "for" step to start the loop and an"end for" to let SVT know where the loop ended. In iTest, all those steps are now nested under the "for" step and the"end for" is removed.
Testbed
SVT and iTest both have Testbed files. As with test cases, there is a one to onemapping between SVT and iTest files. Forevery device specified in SVT, there will be a new device in iTest for everysession type needed by that device. InSVT one could connect using any "protocol" or "session type" to anydevice. In iTest, a new device must bespecified for each "session type".
Devices
DeviceDefinitions in FanfareSVT were made up of to distinctpieces of information.
- Response Maps
- Protocol Specific Information
In iTest, we have split this information up. For every SVT DeviceDefinition we create thefollowing:
- One Response Map Library Project
- One response map for every response map in the original DeviceDefinition.
- One directory with one Session Profile for each "session type" that is imported.
Some general notes about the process.
- As long as you don't specify a destination directory that is inside the locations of FanfareSVT files, your FanfareSVT files will remain untouched.
- All FanfareSVT assets should be collected before performing migration so that all references can be properly linked in iTest
- Any obsolete/invalid assets should be removed before running through migration.
Does this post answer your question? Click the "Accept as solution" button.
Was this post helpful? Click the yellow "Kudos!" button.
