Front-End Test Automation Practices – Record/Playback Enhanced

Posted by Albert Gareev on May 31, 2009 | Categories: Practices

Original date: 3 Mar 2009, 1:00pm

Front-End Test Automation Practices – Record/Playback Enhanced

1. Description
• Parameterized data
• Dataset is a part of the script but not in the code
• Verification via GUI checkpoints (hard-coded)
• Hard-coded flow
• No error handling
• No or limited reporting
• No structure

2. Advantages
• Easy to create
• Quick to create
• No programming required, but expertise on the Testing Tool is a must

3. Disadvantages
• Vulnerable scripts
• No multi-environment support
• Very high maintenance cost for checkpoints
• Not reproducible test results
• Break on any fail
• Limited test flow coverage
• All analysis and validation done manually

4. Applicability
• Single/stable environment
• Short flow Test Cases
• Limited set of checkpoints, as any Database / Data Input change breaks verification and requires recapture
• Short-term simplified automation goals

Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.