---
# System prepended metadata

title: Automation flow

---

# Automation flow

In order to add more quality to the app, the automation flow is now being established

1. The source for the automation tasks is Test Rail. The order to pick up tests is **Priority** field (starting from highest)
2. The test case is considered to be ready for automation when it has **Automation** field set as `to be automated` 
3. When the test is automated, the **Automation** field is set as `Automated` 
4. Whatever is not ready for automation yet, is marked as `Update`
5. When the test case is already automated, but the functionality is changed, then QA updates the Test Rail -> moves the Automation status back to to be automated and notifies the automation guys to update the script, or updates himself, if he can
6. Whatever is never be automated, should be marked as `Not applicable`

![](https://i.imgur.com/m9jNQaN.jpg)

6. QA has to review the tests constantly and provide new tests for automation
7. In case there is nothing in Test Rail in `to be automated`, the concern should be raised in QA channel
8. In case there is too many tests in ready for automation, QA should be based on the `Priority` field to pick up the ones with higher priority first , then going to lower priortiy
9. When updating tests, QA must consider the `Priority` field as an order for automation , so be responsible and dont set everything to `Low` or `Critical`, be wise: super happy path test must be automated first, so it goes with `Critical`, others can be `High` and `Medium`, `Low` test cases probaby wont be automated (at least for now)
