1. Manufacturing
  2. Anywhere Mobility Studio
  3. Setting up and designing Anywhere mobility studio
  4. Test application configuration
  5. Design tests
  6. Design test cases

Define pre and post actions for test case

You can set up a test case event procedure with test actions that are done in a specific sequence. These actions can be done before or after the test case is run. A test case event procedure has one action or a series of actions that are done on a test case event.

Optionally, you can run an action under specific conditions. For conditions, you can use functions that are available for the application.


Developer Developer Tester Tester Start Start Are test actions required  other than the  predefined test actions? Are test actions required  other than the  predefined test actions? Inform developer on  the test action class  to be developed Inform developer on  the test action class  to be developed Develop action class for test action Develop action class for test action You can use a test action for any test case on a: Test case event procedure. If the test case event occurs, the action is done. Test event procedure for a test case step that concerns a button. If the button is clicked, the action is done. For a test action, a class is required. To develop this class, extend the DAWActionRunTestCase class, which is an extension of the DAWActionRun class.Prerequisite: Develop the extension of the DAWActionRunTestCase class in the AOT before you start the steps. Note: The steps are to have the developed test action class uploaded as test action to the related library. Procedure 1. Click Mobility design. 2. Click the Libraries tab. 3. In the list, find and select the desired record. 4. Click View. 5. Click the Test actions tab. 6. Click Refresh. 7. Close the page. Notes If you deploy (export/import) an application as built in Mobility studio, make sure the related custom test action classes are deployed as well. You can do so with a Microsoft Dynamics Lifecycle Services project. Inform tester that  the test action is  available in the library Inform tester that  the test action is  available in the library Update application libraries Update application libraries In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.You link libraries to an application in several ways:Add manuallyYou manually add a library to an application to make it available for use in the application.Link automaticallyIf you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries. Procedure 1. Click Mobility design. 2. On the Applications tab, click Edit. 3. Click the Libraries tab. 4. Sub-task: Manually add library to application. 5. Click Add. 6. In the Library field, enter or select a value. 7. Click Save. Note: As a result, all current actions, functions, and data sets of the library are added to the application. 8. Sub-task: Link used libraries to application. 9. If you have imported an application, you must link the used libraries to the application. Click Link libraries. Note: You can also use this to clean up the list of linked application libraries. The libraries that are not used in the application, are removed from the linked libraries list. 10. Close the page. Are conditions required that use test functions  other than the  predefined test functions? Are conditions required that use test functions  other than the  predefined test functions? Inform developer on  the test function class  to be developed Inform developer on  the test function class  to be developed Develop function class for test function Develop function class for test function You can use a test function for a condition on a test case event procedure action. The test function fills the related value of the condition. For a test function, a class is required. To develop this class, extend the DAWFunctionRunTestCase class. Prerequisite: Develop the extension of the DAWFunctionRunTestCase class in the AOT before you start the steps. Note: The steps are to have the developed test function class uploaded as test function to the related library. Procedure 1. Click Mobility design. 2. Click the Libraries tab. 3. In the list, find and select the desired record. 4. Click View. 5. Click the Test functions tab. 6. Click Refresh. 7. Close the page. Notes If you deploy (export/import) an application as built in Mobility studio, make sure the related custom test function classes are deployed as well. You can do so with a Microsoft Dynamics Lifecycle Services project. Inform tester that  the test function is  available in the library Inform tester that  the test function is  available in the library Update application libraries Update application libraries In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.You link libraries to an application in several ways:Add manuallyYou manually add a library to an application to make it available for use in the application.Link automaticallyIf you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries. Procedure 1. Click Mobility design. 2. On the Applications tab, click Edit. 3. Click the Libraries tab. 4. Sub-task: Manually add library to application. 5. Click Add. 6. In the Library field, enter or select a value. 7. Click Save. Note: As a result, all current actions, functions, and data sets of the library are added to the application. 8. Sub-task: Link used libraries to application. 9. If you have imported an application, you must link the used libraries to the application. Click Link libraries. Note: You can also use this to clean up the list of linked application libraries. The libraries that are not used in the application, are removed from the linked libraries list. 10. Close the page. Set up pre and post actions for test case Set up pre and post actions for test case You can set up a test case event procedure with test actions that are done in a specific sequence. These actions can be done before or after the test case is run. A test case event procedure has one action or a series of actions that are done on one of these test case events: Initializing - The test actions are done before the test case is run After execution - The test actions are done after the test case has been run. For an application event procedure, you can use: The pre-defined test actions. Self-defined test actions - For each of these actions, a self-developed class is required. Use the Up and Down buttons to define the action sequence. Optionally, you can run an action under specific conditions. For conditions, you can use functions that are available for the application. Procedure 1. Click Mobility test manager - Designer. 2. Click the Test cases tab. 3. In the list, find and select the desired record. 4. Click Edit. 5. Click the Events tab. 6. For the desired event, click the + button. 7. On the Actions pane, in the list, select an action. 8. On the Event procedure dialog, on the Actions pane, click Add. 9. Select one or more actions. 10. Click OK. 11. On the Parameters tab, define the action settings. For each action, the parameter fields to be set are defined in the related class. 12. Click the Conditions tab. 13. Click Add and fill in the fields. Note: In the first Value field, you can use a test variable, application variable, or a function. In the second Value field, you can use a test variable, application variable, a function, or a fixed value. 14. Click Close. 15. Close the page. End End Yes No Yes No

Activities

Name Responsible Description

Develop action class for test action

Developer
You can use a test action for any test case on a:
  • Test case event procedure. If the test case event occurs, the action is done.
  • Test event procedure for a test case step that concerns a button. If the button is clicked, the action is done.
For a test action, a class is required. To develop this class, extend the DAWActionRunTestCase class, which is an extension of the DAWActionRun class.
Prerequisite: Develop the extension of the DAWActionRunTestCase class in the AOT before you start the steps.
Note: The steps are to have the developed test action class uploaded as test action to the related library.

Update application libraries

Tester

 		In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.
You link libraries to an application in several ways:
  • Add manually
    You manually add a library to an application to make it available for use in the application.
  • Link automatically
    If you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.
    Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.
If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries.

Develop function class for test function

Developer

 		You can use a test function for a condition on a test case event procedure action. The test function fills the related value of the condition.
For a test function, a class is required. To develop this class, extend the DAWFunctionRunTestCase class.
Prerequisite: Develop the extension of the DAWFunctionRunTestCase class in the AOT before you start the steps.
Note: The steps are to have the developed test function class uploaded as test function to the related library.

Update application libraries

Tester

 		In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.
You link libraries to an application in several ways:
  • Add manually
    You manually add a library to an application to make it available for use in the application.
  • Link automatically
    If you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.
    Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.
If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries.

Set up pre and post actions for test case

Tester

 		You can set up a test case event procedure with test actions that are done in a specific sequence. These actions can be done before or after the test case is run. A test case event procedure has one action or a series of actions that are done on one of these test case events:
  • Initializing - The test actions are done before the test case is run
  • After execution - The test actions are done after the test case has been run.
For an application event procedure, you can use:
  • The pre-defined test actions.
  • Self-defined test actions - For each of these actions, a self-developed class is required.
Use the Up and Down buttons to define the action sequence.
Optionally, you can run an action under specific conditions. For conditions, you can use functions that are available for the application.

Provide feedback