Standards for Test Automation

[article]
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:

  1. Why there is a need for standards in test automation
  2. Things to consider when developing test automation standards
  3. Methods to ensure everyone adopts and follows the standards once they're written

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Oct 12
Oct 15
Nov 09
Nov 09