|« Outline-based Test Plans||Extending a class in Zee »|
Organizations can significantly cut testing cycles by adopting the step-based testing approach to building manual and automated tests. Unlike keyword-driven testing, the step-based approach does not require the development of a test framework. Instead of requiring testing teams to create layers of spreadsheets to define tests and keywords along with supporting files of functions that need to be either recorded or scripted, the step-based approach generates all of the test components based on the objects and actions selected. The keyword-driven approach advertises the division of labor as a benefit. Proponents claim that it allows domain experts to participate in the automation effort. But organizations waste time needlessly because of miscommunication and duplication of effort. The step-based approach allows effective tests to be built by the team members who understand the application whether or not they have programming experience.
Because manual and automated tests are built upon a common structure in the step-based testing approach, transitioning from one to another is a quick and easy process that can be accomplished by the very team members who designed the tests.
The step-based approach was designed to anticipate change. Because tests, test steps and test data are all reusable, there is virtually no duplication. Consequently maintenance is kept to a minimum. When there is one change in the AUT, there is typically one change across test components.
Perhaps the greatest benefit of the step-based approach is the ability that it provides to reuse test components across multiple platforms. Whether your application is moving from a legacy platform to the web/cloud or your organization plans to support applications in both web and mobile environments, test components created around business logic for one version of the application are fully leveraged on subsequent projects. Since only a new object definition is required to reuse all of the existing test components, organizations receive an even larger return on investment with each new project.
Likewise, many organizations have more than one application that perform a similar function but for different customers or users. For example, an eCommerce vendor may have more than one web storefront to cater to various types of buyers. Despite a different user interface, the step-based approach allows the testing components to be reused saving significant time and money.
For more information on step-based testing, visit Zeenyx on the web at www.zeenyx.com