QATechnicals

This blog is all about testing and quality analysis, tools techniques and best practises

Why Automation Testing Framework?

A framework defines the organization’s way of doing things – a ‘Single Standard‘. Following this standard would result in the project team achieving:

Test Library – Process Definition

  • Test Library creation follows a standard design and development process with proper documentation
  • Well-defined process should be established for Team communication, Library versioning and Artifacts creation

Standard Scripting and Team Consistency

  • Scripting standard should be maintained across the framework library creation, which includes business components, system communications, data check points, loggers, reporters etc.
  • Project team should follow the defined scripting standards
  • Published standards across the project team pre-empt the effort involved in duplicate coding, that is prevent individuals from following their own coding standards

Encapsulation from Complexities

  • Test engineers are encapsulated from the complexities and critical aspects of the code
  • Engineers are exposed only to the implemented libraries and tests are executed by just invoking the libraries

Scripts and Data Separation

  • Automation test scripts separated from input data store (for example: XML, Excel files)
  • No modification is required to the test scripts
  • Only input data gets manipulated for testing with multiple input values

Implement and Maximize Re-Usability

  • Establish the developed libraries across the organization/project team/product team, i.e. publish the library and provide access rights
  • Utilities/components shared across the team
  • Usage of available libraries
  • Minimized effort for repeated regression cycles

Extensibility and Maintenance

  • Complete support for application’s new enhancements and existing features modification. For example, re-usable library could be created only for the enhancement features with a minimal effort
  • Standard process for script versioning
  • Role based access rights. For example access rights such as addition, modification and deletion of scripts
  • Project based – Utility/Component access

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.