Automated UI tests
Arguably one of the most painstaking and costly stages of the development cycle is manual certification testing, also called acceptance testing. In a usual non-automated verification cycle, certification testing can take up to 2-3 times longer than the development of a certain feature. Additionally, if previously implemented features are at risk, regression in those areas would have to be executed. In order to increase the release cadence and decrease the development cycles, it is essential that automated UI (or end-to-end ) tests are implemented. This way, the automated pipeline can be verified once and reused to verify the application's UI and integration with other systems, rather than executing manual testing in each ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access