Requirements for a UI Test Framework

							Requirements for a UI Test
       Framework
      Stanislaw Wozniak
         Bernie Miles
                Test authoring
• Flexible scripting language, Object oriented, Easy to learn
• It should be straight forward to write tests and to
  understand the code
• Flexible object recognition engine
• Flexible error handling within the scripts
• Good documentation
• Easy to use, intuitive UI
• Global support 24/5
        Test Maintenance
• Debugging failures – intuitive
• Data driven (data abstraction)
• Maintenance after the production code
  changes should be minimal
• Test code as well as data should support
  versioning so that we can use the
  framework to run our code in any
  environment with any code deployed to it
          Test Execution
• Performance
• Scheduling
• Parallel Execution
• Scalability, easy to add capacity by adding
  more and/or better machines
• Ease of using and setting this up in
  production
Fitness for International Websites
  • Multiple site configuration; ability to
    support multiple UI configurations without a
    need to rework test cases
  • Multi-Browser support
  • Needs to support multi-lingual characters,
    ideally utf8 or utf16
  • AJAX support
        Process Integration
• Detailed logging & reporting. Test reporting should
  be intuitive an easy understand by anyone, not
  only testers
• Integration with SOA test tools and unit test tools
• Test planning software - if you integrate with test
  planning software you can get the idea of
  automation vs. manual coverage, pass rates etc
• Requirements management - integration with this
  tool gives you ability to extract useful information
  such as, requirements coverage