Requirements to Qatts Mapping

Typically, the test requirements for automation are mapped in terms of Features (Groups), Test subjects (Functions), and Objects (UI & Product elements).

1. Explore requirements or test scenarios by executing/navigating manually multiple times with different combinations.

2. Identify Pre conditions, Entry & Exit points

3. Identify Functional test scenarios with all positive/Negative test scenarios.

4. Identify all the Field validations & Element Checks.

5. Click on every actionable UI components. For ex

a. Selecting every Radio button,

b. Changing the drop down options randomly

6. If any changes noticed in the page, like opening up new UI elements, or hiding down any existing UI elements, then these changes should cover in the test scenarios

7. Identify Test data for each test scenario.

8. Create required Features, Functionalities (Test Subjects) with adequate labels and with in-detailed description and map to QATTS

9. Identify UI and Product elements.

10. Create a Functional/Field/Element level Test data sheets by adding all the identified test scenarios with adequate test data details

11. Build the functionality (Field, Element, & Flow)

12. Based Test scenarios, create workflows flows and Automation Scripts (i.e., Action classes)

13. Execute the automation Scripts, Identify the defects, Fix the defects and confirm with screenshots, Test Results and Reports