Você está debatendo a frequência dos testes de regressão com sua equipe. Como encontrar um terreno comum?

- Agreed, prioritizing regression tests based on risk is essential for resource optimization. - High-risk areas like financial transactions indeed need frequent testing. - Reducing test frequency for low-risk changes is a practical approach. - Team discussions on bug impacts can enhance understanding and prioritization. - Overall, this strategy ensures efficient and effective testing.

- I believe it’s not a good approach using automation for regression testing. Cause if in future you add or delete modules to your product it will be hard for testing team to use the same old script for regression or even if you do versioning of script still you required a batch of script as per scenarios. So, I believe it could be more time taking than manual regression. - The good approach is use automation testing for unit testing to identify single units are functioning expectedly and perform regression testing manually.

Agreed that test automation is the best way to execute the feasibile regression test cases. One thing I have found helpful is grouping the automated regression test cases according to the Priority levels. Modularizing the huge regression set into multiple smaller subsets and executing one or more subsets based on time, risk and team capacity. With the well designed automation suite, it is much easier and time saving to run the same tests repeatedly on multiple environments without too much of hassle.

Continuous Integration (CI) is a software development practice where code changes are automatically built, tested, and integrated into a shared repository on a frequent basis. The goal of CI is to detect integration errors early in the development process, ensuring that software components work together smoothly. Developers regularly commit code to a version control system, triggering automated builds and tests. CI pipelines typically include compiling code, running automated tests (unit tests, integration tests), and deploying applications to test environments. By implementing CI, teams can improve collaboration, streamline development workflows, and deliver software updates more reliably and efficiently.

- Integrating regression tests into CI ensures consistent and automated testing. - Helps maintain high testing frequency without manual effort. - Promotes team agreement on testing standards. - Enhances reliability and quality of code integration.

- Acknowledging team capacity is essential when setting test frequency. - Overloading the team can cause burnout and lower test quality. - Open discussions on workload help balance testing efforts. - Sustainable practices ensure effective, long-term testing without straining resources. - Prioritizing team well-being is crucial for success.

- Project stage greatly affects regression test frequency. - Early development stages require more frequent testing due to significant changes. - As the project stabilizes, testing frequency can be reduced. - Team discussions ensure testing strategy adapts to project evolution. - Flexibility is key to effective testing.