DUCOA 15 - UI Control Specific Tasks
There are primarily two types of UI Control or GUI Object specific tasks.
1. Action(s) (Has respective global library functions or routines)
2. Verification(s)
a. Ancillary or Supportive and Preventive (Has respective global functions or routines)
b. Core Test (Has respective global functions or routines)
For any specific TYPE or Class of UI Control or GUI Object, two categories of functions or methods are created. The first category of functions or methods represent the exhaustive list of actions or operations that may be performed on that TYPE or Class of UI Control or GUI Object. Each function or method represents a single action or operation that a user may perform on that TYPE or Class of UI Control or GUI Object.
The second category of functions or methods represent the exhaustive list of verification(s) or checks that may be performed on that TYPE or Class of UI Control or GUI Object. Each function or method represents a single verification or check that a user may perform on that TYPE or Class of UI Control or GUI Object.
A verification or check, however, may be a member of one of these two categories: [1] ‘Core Test’ and [2] ‘Ancillary or Supportive or Preventive’. The verification(s) or checks that belong to the ‘Core Test’ category are the ones that are actually parts of THE TEST. That is, THE TEST can not be completed without performing those verification(s) or checks that belong to this category. Example: Whether a specific value is displayed on a particular UI Control or GUI Object after a specific user-action.
A verification or check that belongs to the ‘Ancillary or Supportive or Preventive’ category is one that is NOT really required to be done to complete THE TEST in question. However, this category of verification or check is required exclusively for building coherent, reliable, robust and synchronized automated tests. Examples: Whether a particular UI Control or GUI Object exists, whether a particular UI Control or GUI Object is enabled, whether a particular UI Control or GUI Object is visible, whether a particular UI Control or GUI Object is clickable etc.
In the context of DUCOA Test Automation Framework Design, the 'Core Test' verification or check functions or methods are designed in a very specific way. Each Core Action and Verification function internally calls the required Ancillary or Supportive or Preventive function(s) before executing its own code that does the intended job. Functions or methods that represent Ancillary or Supportive or Preventive verification(s) are used only through calls made from the functions or methods that represent 'Core Test' verification(s).
Example: A Core Test verification function or method before going ahead with the verification it intends to do on a UI Control or GUI Object, makes calls to the related Ancillary or Supportive or Preventive verification functions or methods that collectively check if that UI Control or GUI Object exists, that UI Control or GUI Object is visible etc. Next Page >>
DUCOA 15 - UI Control Specific Tasks by Debi Prasad Mahapatra is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.
1. Action(s) (Has respective global library functions or routines)
2. Verification(s)
a. Ancillary or Supportive and Preventive (Has respective global functions or routines)
b. Core Test (Has respective global functions or routines)
For any specific TYPE or Class of UI Control or GUI Object, two categories of functions or methods are created. The first category of functions or methods represent the exhaustive list of actions or operations that may be performed on that TYPE or Class of UI Control or GUI Object. Each function or method represents a single action or operation that a user may perform on that TYPE or Class of UI Control or GUI Object.
The second category of functions or methods represent the exhaustive list of verification(s) or checks that may be performed on that TYPE or Class of UI Control or GUI Object. Each function or method represents a single verification or check that a user may perform on that TYPE or Class of UI Control or GUI Object.
A verification or check, however, may be a member of one of these two categories: [1] ‘Core Test’ and [2] ‘Ancillary or Supportive or Preventive’. The verification(s) or checks that belong to the ‘Core Test’ category are the ones that are actually parts of THE TEST. That is, THE TEST can not be completed without performing those verification(s) or checks that belong to this category. Example: Whether a specific value is displayed on a particular UI Control or GUI Object after a specific user-action.
A verification or check that belongs to the ‘Ancillary or Supportive or Preventive’ category is one that is NOT really required to be done to complete THE TEST in question. However, this category of verification or check is required exclusively for building coherent, reliable, robust and synchronized automated tests. Examples: Whether a particular UI Control or GUI Object exists, whether a particular UI Control or GUI Object is enabled, whether a particular UI Control or GUI Object is visible, whether a particular UI Control or GUI Object is clickable etc.
In the context of DUCOA Test Automation Framework Design, the 'Core Test' verification or check functions or methods are designed in a very specific way. Each Core Action and Verification function internally calls the required Ancillary or Supportive or Preventive function(s) before executing its own code that does the intended job. Functions or methods that represent Ancillary or Supportive or Preventive verification(s) are used only through calls made from the functions or methods that represent 'Core Test' verification(s).
Example: A Core Test verification function or method before going ahead with the verification it intends to do on a UI Control or GUI Object, makes calls to the related Ancillary or Supportive or Preventive verification functions or methods that collectively check if that UI Control or GUI Object exists, that UI Control or GUI Object is visible etc. Next Page >>
DUCOA 15 - UI Control Specific Tasks by Debi Prasad Mahapatra is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.
Comments
Post a Comment