Our team building a web app is not confident that a single e2e test suite run would indicate that application is in a desired working state. We would like to improve confidence in our CI/CD pipeline.
We do use code coverage as a primary indicator. However, parts of application are not used or not critical. It is important to mention that e2e testing was an afterthought and parts of application are not covered.
I would like to discover optimal way on how to prioritize discovery and writing of missing tests, furthermore increasing confidence in our test suite as a whole.
What approach could be taken in this situation?
Aucun commentaire:
Enregistrer un commentaire