You can exchange the test setup to run the same tests on another environment. You can do so on several levels.

Tester Tester Start Start Export test case Export test case You can export a test case to an XML file. So, you can import the test case in another Microsoft Dynamics 365 for Operations environment. You can find and download the created file on the Mobility sharing workspace, on the Data files tab. What is included in the export depends on the export type: Only test case For all selected test cases, this is included in the export: General test case settingsStepsTest variablesEvents Only test scenario For all selected test cases, only the test scenarios are included in the export.Test case & test scenario For all selected test cases, everything is included in the export. If you export a test case, consider this: The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios. An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios. Procedure 1. Click Mobility test design. 2. Click the Test cases tab. 3. In the list, find and select the desired test cases. 4. Click Export. 5. Select Yes in the Generate package field. 6. In the File name field, type a value. 7. In the Export type field, select an option. 8. Click OK. 9. Click Share. 10. On the Data files tab, in the list, find and select the desired file. Note: A data file with the file name extension: - .dawdata is an XML file. - .zip is a data package. 11. Click Download. Export test scenario Export test scenario Procedure 1. Click Mobility test design. 2. Click the Test cases tab. 3. In the list, find and select the desired test case. 4. Click Edit. 5. Click the Test scenarios tab. 6. In the list, find and select the desired test cases. 7. Click Export. 8. Select Yes in the Generate package field. 9. In the File name field, type a value. 10. Click OK. 11. Close the page. 12. Click Share. 13. On the Data files tab, in the list select the desired file. Note: A data file with the file name extension: - .dawdata is an XML file. - .zip is a data package. 14. Click Download. Export test suite Export test suite You can export a test suite to an XML file. So, you can import the test suite in another Microsoft Dynamics 365 for Operations environment. You can find and download the created file on the Mobility sharing workspace, on the Data files tab. If you export a test suite, this setup is always included: General test suite settings The related test cases Which parts of the related test cases are included in the export depends on the export type: Only test case For all related test cases, this is included in the export: General test case settingsStepsTest variablesEvents Only test scenario For all selected test cases, only the test scenarios are included in the export.Test case & test scenario For all selected test cases, everything is included in the export. If you export test cases, consider this: The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios. An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios. Procedure 1. Click Mobility test monitoring. 2. On the Test suites tab, in the list, find and select the desired test suites. 3. Click Export. 4. In the File name field, type a value. 5. Select Yes in the Generate package field. 6. In the Export type field, select an option. 7. Click OK. 8. Click Share. 9. On the Data files tab, in the list, find and select the desired file. Note: A data file with the file name extension: - .dawdata is an XML file. - .zip is a data package. 10. Click Download. Export test plan Export test plan You can export a test plan to an XML file. So, you can import the test plan in another Microsoft Dynamics 365 for Operations environment. You can find and download the created file on the Mobility sharing workspace, on the Data files tab. If you export a test plan, this setup is always included: General test plan settingsRelated test suitesGeneral test suite settings of related test suites The related test cases Which parts of the related test cases are included in the export depends on the export type: Only test case For all related test cases, this is included in the export: General test case settingsStepsTest variablesEvents Only test scenario For all selected test cases, only the test scenarios are included in the export.Test case & test scenario For all selected test cases, everything is included in the export. If you export test cases, consider this: The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios. An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios. Procedure 1. Click Mobility test monitoring. 2. Click the Test plans tab. 3. In the list, find and select the desired test plans. 4. Click Export. 5. In the File name field, type a value. 6. Select Yes in the Generate package field. 7. In the Export type field, select an option. 8. Click OK. 9. Click Share. 10. On the Data files tab, in the list, find and select the desired file. Note: A data file with the file name extension: - .dawdata is an XML file. - .zip is a data package. 11. Click Download. Usually, export and import  is done on different environments. So, move the data files accordingly. Usually, export and import  is done on different environments. So, move the data files accordingly. Import configuration Import configuration You can import a configuration from an XML file. This XML file must be the result of a configuration export from Mobility studio on another or the current Microsoft Dynamics 365 for Operations environment. The steps in this topic show how to import a configuration file that is stored on the file share. Make sure the file is already uploaded as type Data file to the Mobility sharing workspace. You can also import a configuration file from: A file location on your computer. To do so, in the File location field, select File on file share. Browse for the file on your computer. On selection, the file is automatically uploaded as type Data file to the Mobility sharing workspace. A file location on the server on which Microsoft Dynamics 365 for Operations is running. Only use this option for big configuration files. Procedure 1. Click Mobility management. 2. Click Import Wizard. 3. In the list, find and select the desired record. 4. Click Next. 5. Click Finish. End End

Activities

Name Responsible Description

Export test case

Tester

You can export a test case to an XML file. So, you can import the test case in another Microsoft Dynamics 365 for Operations environment.
You can find and download the created file on the Mobility sharing workspace, on the Data files tab.
What is included in the export depends on the export type:
  • Only test case
    For all selected test cases, this is included in the export:
    • General test case settings
    • Steps
    • Test variables
    • Events
  • Only test scenario
    For all selected test cases, only the test scenarios are included in the export.
  • Test case & test scenario
    For all selected test cases, everything is included in the export.
If you export a test case, consider this:
  • The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.
  • A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios.
  • An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.

Export test scenario

Tester

Export test suite

Tester

You can export a test suite to an XML file. So, you can import the test suite in another Microsoft Dynamics 365 for Operations environment.
You can find and download the created file on the Mobility sharing workspace, on the Data files tab.
If you export a test suite, this setup is always included:
  • General test suite settings
  • The related test cases
Which parts of the related test cases are included in the export depends on the export type:
  • Only test case
    For all related test cases, this is included in the export:
    • General test case settings
    • Steps
    • Test variables
    • Events
  • Only test scenario
    For all selected test cases, only the test scenarios are included in the export.
  • Test case & test scenario
    For all selected test cases, everything is included in the export.
If you export test cases, consider this:
  • The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.
  • A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios.
  • An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.

Export test plan

Tester

You can export a test plan to an XML file. So, you can import the test plan in another Microsoft Dynamics 365 for Operations environment.
You can find and download the created file on the Mobility sharing workspace, on the Data files tab.
If you export a test plan, this setup is always included:
  • General test plan settings
  • Related test suites
  • General test suite settings of related test suites
  • The related test cases
Which parts of the related test cases are included in the export depends on the export type:
  • Only test case
    For all related test cases, this is included in the export:
    • General test case settings
    • Steps
    • Test variables
    • Events
  • Only test scenario
    For all selected test cases, only the test scenarios are included in the export.
  • Test case & test scenario
    For all selected test cases, everything is included in the export.
If you export test cases, consider this:
  • The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.
  • A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios.
  • An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.

Import configuration

Tester

You can import a configuration from an XML file. This XML file must be the result of a configuration export from Mobility studio on another or the current Microsoft Dynamics 365 for Operations environment.
The steps in this topic show how to import a configuration file that is stored on the file share. Make sure the file is already uploaded as type Data file to the Mobility sharing workspace.
You can also import a configuration file from:
  • A file location on your computer. To do so, in the File location field, select File on file share. Browse for the file on your computer. On selection, the file is automatically uploaded as type Data file to the Mobility sharing workspace.
  • A file location on the server on which Microsoft Dynamics 365 for Operations is running. Only use this option for big configuration files.

Activities

Name Responsible Description

Export test case

Tester

You can export a test case to an XML file. So, you can import the test case in another Microsoft Dynamics 365 for Operations environment.
You can find and download the created file on the Mobility sharing workspace, on the Data files tab.
What is included in the export depends on the export type:
  • Only test case
    For all selected test cases, this is included in the export:
    • General test case settings
    • Steps
    • Test variables
    • Events
  • Only test scenario
    For all selected test cases, only the test scenarios are included in the export.
  • Test case & test scenario
    For all selected test cases, everything is included in the export.
If you export a test case, consider this:
  • The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.
  • A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios.
  • An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.

Export test scenario

Tester

Export test suite

Tester

You can export a test suite to an XML file. So, you can import the test suite in another Microsoft Dynamics 365 for Operations environment.
You can find and download the created file on the Mobility sharing workspace, on the Data files tab.
If you export a test suite, this setup is always included:
  • General test suite settings
  • The related test cases
Which parts of the related test cases are included in the export depends on the export type:
  • Only test case
    For all related test cases, this is included in the export:
    • General test case settings
    • Steps
    • Test variables
    • Events
  • Only test scenario
    For all selected test cases, only the test scenarios are included in the export.
  • Test case & test scenario
    For all selected test cases, everything is included in the export.
If you export test cases, consider this:
  • The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.
  • A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios.
  • An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.

Export test plan

Tester

You can export a test plan to an XML file. So, you can import the test plan in another Microsoft Dynamics 365 for Operations environment.
You can find and download the created file on the Mobility sharing workspace, on the Data files tab.
If you export a test plan, this setup is always included:
  • General test plan settings
  • Related test suites
  • General test suite settings of related test suites
  • The related test cases
Which parts of the related test cases are included in the export depends on the export type:
  • Only test case
    For all related test cases, this is included in the export:
    • General test case settings
    • Steps
    • Test variables
    • Events
  • Only test scenario
    For all selected test cases, only the test scenarios are included in the export.
  • Test case & test scenario
    For all selected test cases, everything is included in the export.
If you export test cases, consider this:
  • The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import.
  • A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios.
  • An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.

Import configuration

Tester

You can import a configuration from an XML file. This XML file must be the result of a configuration export from Mobility studio on another or the current Microsoft Dynamics 365 for Operations environment.
The steps in this topic show how to import a configuration file that is stored on the file share. Make sure the file is already uploaded as type Data file to the Mobility sharing workspace.
You can also import a configuration file from:
  • A file location on your computer. To do so, in the File location field, select File on file share. Browse for the file on your computer. On selection, the file is automatically uploaded as type Data file to the Mobility sharing workspace.
  • A file location on the server on which Microsoft Dynamics 365 for Operations is running. Only use this option for big configuration files.
Related to Notes

Exchange test setup

 

Provide feedback