Automation Testing

Automation Objectives Nexus

Objectives

  • To reduce the regression cycle time
  • To improve test coverage
  • To reduce cost
  • To improve traceability
  • Providing a central repository for all test artifacts

Test Case Selection Criteria

  •  Test cases requires the verification and validation of multiulle attributes, objects and components
  •  Test cases needs to be executed with external data that resides in a database system or spreadsheet
  •  Test cases will be used for security testing
  •  Test cases will be used for regression, functional testing
  •  Test cases will be used to validate values, calculations, etc, displayed on a customized report, or online report
  •  Test cases will be repeated many times or is highly repetitive (i.e Test script will need to be executed multiple times on different software releases or builds)
  •  Test script will be played back with multiple sets of data (i.e. Data driven scripts, parameterized scripts)
  •  The application under test has a stable environment with repeatable conditions
  •  Test script will be used for integration testing and requires correlation across multiple business processes.
Test Criteria Nexus
Automation Testing Guidelines Nexus

Guidelines for Automation

  • Full time dedicated resources
  • Well-articulated test framework
  • Application independent test framework
  • Development of common components for different applications
  • Module independence
  • Framework independent test strategy/design vocabulary
  • Clear demarcation between test framework designers and Automation team.

Let’s get started

Still have questions?

Software testing ensures the reliability of applications: manual testing for user experience, automation for efficiency, performance for speed, and security for data protection.