GeekArticles 
Testing LoadRunnerTest Automation: An Architected Approach
Author: stickyminds.com |
Published: 18th Aug 2005 |
Visited: 742 times |
Add CommentFiled in: LoadRunnerIn the world of automated testing, everyone throws around buzzwords like "data-driven," "data flows" and "error handling," but what does it take to produce automation that is efficient, maintainable and usable? Successful automated testing requires a considerable financial investment. Simply installing an automated testing tool and recording scripts may jumpstart the initial automated testing effort, but this approach will become difficult to maintain and therefore more expensive. A more cost-effective solution is an architected solution. Providing the right architectural framework for automation development means that the automation code can be used for longer periods of time with less maintenance than a simple record/playback solution. This translates to a significant savings over the course of longer projects, and the ability to more thoroughly test an application with less employee overhead. The particular architecture championed here is based on the idea of automation code as an application in its own right. Code reuse, encapsulation (on many levels), recursion, object-oriented concepts, testing maturity and usability (of automation by non-technical business analysts) are covered. The result of this architecture is reliable automation code with scripts that can last the entire life of the product (not just the project) and that can be used and enhanced by business analysts who have little to no knowledge of automated testing.
Read Article Sponsored Links
Related Articles
• Swing Extreme Testing - Outline of the Unit Test Outline of the Unit Test
The things we want to test are:
Initial settings:
The text field is empty.
The text field is a sensible size.
The Ok button is disabled.
The Cancel button is enabled.
The dialog is a sensible size.
...
• Swing Extreme Testing - Unit Test Infrastructure Unit Test Infrastructure
Having seen the broad outline of the test class and the UI methods needed, we can look closely at the implementation of the test. start with the UI Wrapper class and the init() and cleanup()method ...
• Swing Extreme Testing - The wasCancelled() Test The wasCancelled() Test
The first of our API tests is to check the wasCancelled() method. We will basically do three investigations. The first test will call wasCancelled()before the dialog has been cancelled. The second test will cancel the dialog and then call the method. In the third test we wil ...
• Swing Extreme Testing - The Data Validation Test The Data Validation Test
The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid. A name can be invalid if it contains an illegal character, or if it has already been use ...
• SOA Approach to Integration Book Review Book Review: SOA Approach to Integration
XML, Web services, ESB, and BPEL in real-world SOA projects
Businesses will always need highly efficient applications which have ability to provide outstanding user experience while maintaining security. Most of the developers today thrive in a business set ...
• SOA Web Services - SOA and Web Services Approach for Integration SOA and Web Services Approach for Integration
In Chapter 2, you were introduced to how Service-Oriented Architecture (SOA) can be used for application integration. We saw that the integration itself may be restricted within an Enterprise or may involve third parties (B2B or B2C). Service-Oriented A ...
