Overcome script maintenance
Nowadays, team leads spend time optimizing their team velocity and efficiency. A key blocker to team velocity, among others, is the stream of defects discovered late in the process: either at the end of the sprint or worse, by real users in production. The decision to make a process change is obvious, and the natural strategy is to pursue large-scale test automation to offer reasonable coverage. The reality though, is that after creating 10 scripts for several platforms, and a week has passed, your team is getting into the spiral of script maintenance and the vision of fast effort for scalable, stable test automation is not so fast anymore.
Continuous delivery means fast implementation
The Phoenix, a leading insurance provider, was facing one such challenge. With a corporate strategy to become agile and lead their market via digital transformation; test coverage was a necessary component to attend to. Turning all 45 testers with varying coding skills and experience onto test automation was far from obvious.
One of the key criteria to decide on the direction was a significant undertaking of the test framework, and more specifically, alignment with the organizational existing toolchain, and the ongoing maintenance effort that is required. The former required significant, gradual, and long enablement process for all testers and developers, including changes to the toolchain in use. The latter included considerations of ongoing maintenance of the test scripts, and the ever-changing object repository. In addition, Selenium is continuously in flux, and the framework needs to be maintained and updated. In other words, creating a test management framework is a huge effort in itself, and is very difficult to scale and maintain stability.
Instead, implementation of codeless testing methodology instantly offered significant benefits: testers were immediately enabled to visually author the initial version of many test scripts. No effort was required from developers, those test cases were easily added to the CI toolchain for continuous testing. More importantly, the virtue of self-correcting codeless solution means that the tests are more stable, and the testers can focus on scaling the coverage and attach themselves to the squad, creating coverage for features as those are created.
Test automation measurable metrics
Selecting codeless testing enabled The Phoenix to achieve significant coverage within an amazingly short period. The direct impact can be shown below. Granted, scriptless methods will not achieve 100% coverage, and so some of the 45 testers turned into test coders for the more complex cases.
The real benefit for The Phoenix can be the indirect, organizational impact and the quality of the product to end users. Internally, the organization was better prepared to transform their digital presence and lead the market. Developers gained earlier insight into defects and are able to resolve those quickly and return to their jobs developing. The operations team are receiving a build that is better tested and offers a more mature product. Certainly, for end users, the outcome is a product that is more compelling, richer in functionality, and offers better quality.
End-to-end codeless testing
As team leads are deciding on the direction and phases to enable continuous quality, codeless testing can offer almost immediate measurable benefits to any organization. Almost no changes are required and the teams can focus their attention on innovation while developing test coverage for the more complex flows. This hybrid approach enables a sustainable long-term strategy that offers a great balance to everyone in the organization and customers.