Automation Framework Features List


Before Automation Framework can be developed, it goes through the requirement phase, where list of features are discussed with stakeholders and prioritized.  Here is list (subset) of features related to automation framework that can be discussed, prioritized and scoped for the automation testing framework.


Core Features
  • Platform & OS independence
  • Technology & application independence
  • Data driven capabilities (Input Data, output data, meta data)
  • Test large volume of data quickly
  • Framework should be driven through table / key words
  • Shared software library for automation scripts should be implemented
  • Record & playback functionalities
  • Ability to parameterize (recorded) scripts
  • Should have end-2-end testing capability to cover business scenarios
  • Capability to preparing / cleaning the test environment
  • Resource management of test / lab resources
  • View and edit test cases intuitively
  • Ability to implement dynamic conditions
  • Ability to implement dynamic loop support 


Execution
  • UI to execute tests
  • Support for parallel execution of test cases
  • Support for selected execution of test cases
  • Support for cancellation of test execution
  • Support for running failed test cases
  • Support for running grouped test cases
  • Support for running prioritized test cases
  • Ability to control the length of execution time
  • Support for nested test cases
  • Ability to import modules at run time
  • Support unattended test run for integration with build processes and batch runs.
  • Support distributed execution environment (distributed test bed)
  • Support distributed SUT
  • Update test metrics automatically
  • Easy debugging and logging


Reporting
  • Should be able to generate concise report automatically
  • Report should provide where errors occurred and using which test data
  • Report should be easily sharable
  • Report should have details for each step execution
  • Report should have snapshots for failed tests
  • Screenshots for every / failed steps
  • Customizable reporting (DB Access, crystal reports etc.)
  • Automated notifications on failure or reaching threshold level


Integration with Other Tools
  • Framework should be able to integrate with spreadsheets / databases
  • It should be able to integrate with nightly continuous build
  • Versioning of test scripts
  • Logging of defects automatically


General
  • Extensible and Customizable (Open API to be able to integrate with other tools)
  • Test framework should be loosely / tightly coupled with application-under-test (AUT)
  • It should be reliable and consistent in result reporting
  • Documentation for administration / test script creation
  • Less dependence on highly skilled automation professionals
  • Easy to use, integrate and maintain


Others
  • Should have instrumentation for debugging purpose

Comments

Post a Comment

Popular posts from this blog

Performance Test Run Report Template

You have gathered requirements from clients, identified key critical business scenarios, analyzed the workload distributions, found out performance goals and requirements, identified  tool for generating load, setup the test environment, designed the scripts, executed the performance run, collected the raw data, analyzed it, what next?  Send information to stakeholders? No!!  Wait!! It needs to formatted, customized for different stakeholder(s) and reported accordingly. This article suggests one of the ways to report performance run results to client especially if the performance testing activity has been outsourced to yours company.  It discusses the performance report template and importantly the reasons for including the items in the report. The performance report template contains information by data collected from client side only and doesn’t discuss / talk about data from server side like processor utilization etc. Broadly the performance report has been divided in three major
Read more

Understanding Blockchain

This notes will cover below questions... Introduction to Blockchain What is the difference between Blockchain and Bitcoin? What are some other uses of blockchain that go beyond bitcoin? History of blockchain Could you explain the blockchain process in laymen terms? If all data is available to the public. Can anyone know my bank balance (in Bitcoin)? Introduction to Blockchain The Blockchain is a decentralized and distributed public (digital) ledger where transactions are recorded and confirmed anonymously. It’s a record of events that is shared between many parties. More importantly, once information is entered, it cannot be altered without altering subsequent blocks. WTF is the blockchain? A guide for total beginners What is the difference between Blockchain and Bitcoin? The blockchain is a technology
Read more

Bugs Management in Agile Project

Agile has a refreshing approach to bugs, especially when contrasted with traditional waterfall practices. Historically, teams would postpone bugs to a stabilization phase. This stabilization phase was long and tedious, typically with high stress and long hours. Agile, on the other hand, promotes the following thought processes: Carrying bug debt is unhealthy and sometimes, even destructive. We should fix bugs, not track them. A feature isn't done until the bugs are fixed. Quality is part of the overall cost. Bugs are prioritized against new features. A bug needs to be more important than the next new feature. Notes All new features have a "bug tail." The bug tail is the diminishing number of open bugs on the new functionality. When a feature is added, bugs are introduced. Most are discovered and fixed immediately by the team as a part of feature development: some a few days later, others not until long after a story is considered &quo
Read more