Basing an automated testing effort on using only a capture tool such as IBM Rational® Robot to record and play back test cases has its drawbacks. Running complex and powerful tests is time consuming and expensive when using only a capture tool. Because these tests are created ad hoc, their functionality can be difficult to track and reproduce, and they can be costly to maintain.

A better choice for an automated testing team that’s just getting started might be to use a test automation framework, defined as a set of assumptions, concepts, and practices that constitute a work platform or support for automated testing.

Here are five test automation frameworks that an automated testing team might consider using instead of relying only on a capture tool.

Related Articles

• 30-second Selenium installation tutorial (0)
• Why Thinking ‘Inside the Box’ Is Sometimes Effective for Test Automation (0)
• Advances in Automated Software Testing Technologies (0)
• Next-generation requirements traceability automation tool - TBreq v3.0 (0)
• Automate web app testing across many platforms with Selenium (0)