XMind

GUI Step Automation

1. SEED

   1. Synchronize

      1. Wait for the Object reaching expected state (E.g. EXISTS, ENABLED, DISPLAYED) within default or defined timeframe

   2. Exists

      1. Object's logical name or ph. description is available

      2. Object's parent (Window, Form, etc.) successfully returned the instance

      3. Object's instance is valid ( != NULL)

      4. EXISTS on GUI form

   3. Enabled

      1. Parent GUI form is enabled

      2. The Object is enabled

      3. The Object is not busy

   4. Displayed

      1. The Object is not covered by another GUI element

2. NATA

   1. Number of Arguments

      1. Number of arguments to pass in matches number of arguments Object's method can accept

   2. Type of Arguments

      1. Type of arguments to pass in matches type of arguments Object's method can accept

      2. Type of supplied data matches types that Object's method can accept

3. LI

   1. Log

      1. Negative reporting: report ALL fails occurred

      2. Positive reporting: report success for major steps

      3. Report names of the steps executed

      4. Report any business data used for input, retrieved from AUT, or used in verification

      5. Report PASS conditions used

      6. Report FAIL conditions used

      7. Report cut-off conditions used (timeout, etc.)

   2. Investigate

      1. Capture any pop-up messages

      2. Capture Application, Window, and Object state

      3. Match actual state model with defined state model, report per component

1. Albert Gareev http://automation-beyond.com/