DUCOA 17 - Test Composition Process
I have explained the Test Translation Process earlier on this whitepaper. I would like to share a bit of additional information, in the context of the Test Translation Process and some refinement there in, here. Following are the steps that are performed in this translation process:
1. Thoroughly review and analyze the Translated Test to gather information for the next step.
2. In case the Test Automation Engineering or Development Team finds that a few more granular steps are required to be added to this list of steps, in the Translated Test, to make it really complete, reliable, robust and synchronized, those are added. These could be the steps that are not very obvious from a Functional Testing point of view; but are absolutely important from the Test Automation perspective.
Examples: Waiting for a UI control to attain a specific state, Waiting or checking for a UI Control’s attribute or property to attain a specific value, Resizing or moving or dragging or scrolling a specific UI Control to make the state of the AUT or SUT ready for the next operation (Action or Verification). NOTE: Ensure that there are no ‘side-effects’ of these intermediate or supporting (Ancillary or Preventive) additional steps on THE TEST!
3. Pertaining to each granular UI Control or GUI Object Level Action or Verification step:
a. The corresponding function name (Control Action or Operation and Verification Function Name) is added.
b. Parameter Values (UI Control | GUI Object Identification Details etc.) are added.
c. The Input Data and Expected Output Data (Text or Number to be entered, Item to be Selected etc.) are added.
Notes:
1. This makes it the Composed Test ready as an input to the Test Automation Platform or Infrastructure or Framework.
2. There is something special about the “Drag and Drop” UI Control or GUI Object Level Action or Operation. What is special about this Action or Operation is, it is not about just one UI Control or GUI Object. This Action or Operation involves two UI Controls or GUI Objects; the source and the destination. That is why, in this case, UI Control Parameters (to identify, locate or find and discover the UI Control or GUI Object in question) pertaining to both (the source and the destination) are used to get done with this operation. Next Page >>
DUCOA 17 - Test Translation in Automation Scope by Debi Prasad Mahapatra is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.
1. Thoroughly review and analyze the Translated Test to gather information for the next step.
2. In case the Test Automation Engineering or Development Team finds that a few more granular steps are required to be added to this list of steps, in the Translated Test, to make it really complete, reliable, robust and synchronized, those are added. These could be the steps that are not very obvious from a Functional Testing point of view; but are absolutely important from the Test Automation perspective.
Examples: Waiting for a UI control to attain a specific state, Waiting or checking for a UI Control’s attribute or property to attain a specific value, Resizing or moving or dragging or scrolling a specific UI Control to make the state of the AUT or SUT ready for the next operation (Action or Verification). NOTE: Ensure that there are no ‘side-effects’ of these intermediate or supporting (Ancillary or Preventive) additional steps on THE TEST!
3. Pertaining to each granular UI Control or GUI Object Level Action or Verification step:
a. The corresponding function name (Control Action or Operation and Verification Function Name) is added.
b. Parameter Values (UI Control | GUI Object Identification Details etc.) are added.
c. The Input Data and Expected Output Data (Text or Number to be entered, Item to be Selected etc.) are added.
Notes:
1. This makes it the Composed Test ready as an input to the Test Automation Platform or Infrastructure or Framework.
2. There is something special about the “Drag and Drop” UI Control or GUI Object Level Action or Operation. What is special about this Action or Operation is, it is not about just one UI Control or GUI Object. This Action or Operation involves two UI Controls or GUI Objects; the source and the destination. That is why, in this case, UI Control Parameters (to identify, locate or find and discover the UI Control or GUI Object in question) pertaining to both (the source and the destination) are used to get done with this operation. Next Page >>
DUCOA 17 - Test Translation in Automation Scope by Debi Prasad Mahapatra is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.
Comments
Post a Comment