# Weekly Regression Testing

### Purpose of this

The main purpose of this activity is to bring more testing and quality to master build and reveal more bugs more often

### General approach

1. Each Monday-Tuesday latest master build is being picked up for full regression testing, which means all existing tests should be executed (of possible and time permits)
2. During the testing QA logs the tickets
3. During testing QA updates any reasonable number of test cases in test rail to help the team to keep the test documentation up to day
4. By the end of Tuesday QA responsible for this task posts the results in QA group, the results should contain valuable info:
* bugs logged durung testing of this regression round. This is important because Iury will plan the iteration for devs including this info
* test cases that were refactored / updated / removed
* which areas were covered (if not all) -> test run link should be sufficient

### Who is responsible?

We want to introduce rotation, that will occur on weekly basis, at least for the first round, the exact order can be set either in channel or be written somewhere visible