A Case Study
Summary:
The Mocrosoft Windows team has transitioned from having no standards to having a strict set of guidelines to follow when writing new automated tests.
Over the last five years, I've had the opportunity to work in a group who writes automated tests using retail Windows applications to ensure compatibility in future releases of Windows, and to find bugs in the operating system. During that time, we have transitioned from having no standards to having a strict set of guidelines to follow when writing new automated tests.
We have seen many benefits as a result of developing standards. In this paper, I will talk about these three areas:
- Why there is a need for standards in test automation
- Things to consider when developing test automation standards
- Methods to ensure everyone adopts and follows the standards once they're written
