Automated tests require an initial time effort, but once completed, they start to produce positive revenue, so they are a great choice!

Critical and repetitive test cases are the ones that are eligible to be automated, in order to add value to the process.

Moving from Manual to Automated Tests | TestRail Quality HubTestRail  Quality Hub

How does this process work?

1. Project initiation

  • Define the tool we are going to use for our test automation.
  • Define the execution environment (browsers, devices).

2. Automation Feasibility Analysis

  • Review the documentation and the test cases that are already on our regression plans and test suites.
  • Review which test cases can be solved by Test Automation.

3. Environment setup

  • Define which type of implementation is going to be used. In order to assess what can be done, we need to pick some of the test cases and develop automated test scripts for them.

4. Script Development

  • Start developing scripts for all the test cases that were agreed to be automated.

5. Execution and analysis

  • Once the test scripts are developed they can be executed. After executing them we can analyze if they passed the conditions that were set on the test script (based on the acceptance criteria and the expected outcome)

6. Metrics, reports, and error handling

  • Once the test execution is finished, a report is sent with metrics of which of the cases passed and which not. With this data, in case of failure, an assessment is performed, and if needed a bug is reported.

7. Regression test

  • The cycle now starts at this point. All the test case scripts are implemented and ready to run. Now the life cycle starts to loop between this step and the sixth, a regression is run, its reports are obtained and assessed, and errors are reported.

8. Maintenance

  • When the acceptance criteria changes or a different dataset is needed, the test case scripts are developed with a possible change already in mind, so they can be maintained and test what is expected from them.
Display Automated JIRA Test Results in Testy | ALM Works Blog