Migrate Microsoft RSAT test suites to Leapwork: FAQ

Migrate Microsoft RSAT test suites to Leapwork: FAQ

1. Do I still need to use Command Prompt?

Ans. No. The migration process is now performed entirely through the RSAT to Leapwork Migration Wizard.

2. What folder should I select for migration?

Ans. Always select the parent RSAT project folder. Selecting an individual flow or test suite folder is not supported.

3. What happens during the Analyze RSAT Files step?

Ans. The Migration Wizard analyzes your RSAT project, identifies test cases and blocks, detects migration issues, validates configurations, and recommends any changes that should be reviewed before exporting.

4. What do the migration warnings mean?

Ans. Warnings are informational and highlight items that you may want to review. They do not necessarily prevent the migration from completing and can be skipped if appropriate.

5. What are Risky blocks?

Ans. Risky blocks are blocks that may require manual review or updates because they contain configurations that cannot be migrated automatically.

6. Can I update migration settings before exporting?

Ans. Yes. You can review and update settings such as Active Row values, login configurations, target selectors, and other supported settings directly in the Migration Wizard before exporting.

7. What is the Matching Blocks section used for?

Ans. Matching Blocks helps you identify similar or related blocks so you can apply consistent updates across multiple flows.

8. What is the difference between "Only this selected flow" and "Apply to all login blocks"?

Ans.

9. What is a Review Session?

Ans. A Review Session lets you save your migration review progress so you can continue later without reanalyzing the entire RSAT project.

10. What are Reusable Preferences?

Ans. Reusable Preferences allow you to save commonly used settings, such as D365 login information, and automatically apply them to future migrations.

11. Can I send migrated flows directly to Leapwork?

Ans. Yes. Enable Send to Leapwork, provide the required Controller URL, Target Folder, Team ID, and API Key, then upload the migrated flows directly from the Migration Wizard.

12. Can I reuse the exported package?

Ans. Yes. The exported ZIP package can be imported into Leapwork multiple times.

13. Can I modify flows after migration?

Ans. Yes. Once imported, all edits should be made directly in Leapwork Studio.

14. Do I need to rerun the migration after making changes in Leapwork?

Ans. No. Changes made inside Leapwork remain within Leapwork. Only rerun the migration if your original RSAT project has changed.

15. My migrated flows are missing after import. What should I check?

Ans. Make sure you imported the exported migration package (or its extracted folder), not the original RSAT project. Also verify that the migration completed successfully before importing.

16. Why can't the Migration Wizard find my flows?

Ans. Verify that you selected the parent RSAT project folder. Selecting an individual test suite or flow folder is not supported and will prevent the Migration Wizard from finding your flows.

17. Why are my migrated flows missing after import?

Ans. Ensure that you imported the exported migration package (or its extracted folder) into Leapwork Studio, rather than importing the original RSAT project.

18. Can I modify migrated flows after importing them into Leapwork?

Ans. Yes. After the migration has been imported into Leapwork Studio, all future updates should be made directly in Leapwork. You only need to rerun the migration if changes are made to the original RSAT project.