As Software/Product releases cycles are getting quicker and companies implementing Agile methodologies for their engineering product development, it’s very difficult for companies to deliver quality software/product within one/two sprints.
With continuous integration (CI) there are chances quality of the product needs to be evaluated (System, Feature Regression) at quicker pace before pushing builds to production using CD.
Continuous testing downstream activity of Continuous Integration helps in quickly running tests especially automated tests for all the software builds generated by the CI pipeline. This will help in the qualifying every commits made product.
Maintain Quality with Continuous Testing
For StartUps the focus is mainly on getting product ready for their customer with limited set of team members in their Agile teams (dev+qa). There is continuous churning of code and there are chances that product hits huge regression and new feature issues. It’s better to manage less gap between Feature development and automated tests so that as product evolves test automation gap is very minimal.
For Startups/companies to maintain their features stable, it better to have automated tests in places in line with feature development and run as part of Continuous Testing activite.
In case if they find problem with adding automated tests, it’s better to have few dedicated resources/ dev resources add those automatest tests and run them as part of CI/CD pipeline.