Skip to main content

Guideline Overview

1. Overview​

The purpose of this document is to provide an overview of the automated testing guidelines for testing application code.

This document covers guidelines and best practices for automated testing and provides a high-level overview of the following topics. Detailed documentation for each topic will be created and shared separately.

2. Automated Testing Design Architecture​

Automation testing is a software testing technique that uses automated tools to execute test cases. These tools can:

  • Enter test data into the system under test
  • Compare expected and actual results
  • Generate detailed test reports

Automated testing is important for the following reasons:

  • Manual testing of all workflows, fields, and negative scenarios is time-consuming and costly
  • Difficult to test multilingual applications manually
  • Does not require human intervention (can run unattended, e.g., overnight)
  • Increases the speed of test execution
  • Improves overall test coverage

For more details:
Automated Testing Design Architecture

3. Automated Testing Technology Stack Selection​

The technology stack plays a critical role in software performance across the SDLC. It enables organizations to build, deploy, and monitor applications effectively.

An effective tech stack should be:

  • Cost-effective
  • Scalable
  • Flexible
  • Easy to set up
  • Capable of advanced integrations

For more details:
Automated Testing Technology Stack Selection

4. Performance Testing​

Performance testing is a non-functional testing method used to evaluate system performance under different conditions.

It measures:

  • Responsiveness
  • Stability under varying workloads
  • System behavior under different network conditions

This includes:

  • Load testing
  • Stress testing
  • Testing in both lab and production-like environments

The goal is to determine system speed and reliability under expected and extreme conditions.

For more details:
Performance Testing

5. Security Testing​

Security testing is a type of non-functional testing focused on identifying vulnerabilities and ensuring application security.

Key practices include:

  • Regular automated security testing using up-to-date tools
  • Increasing security knowledge across the organization
  • Providing easy-to-understand reports
  • Supporting compliance and security teams

For more details:
Security Testing

6. Automated Testing Configuration Guideline​

For more details:
Automated Testing Configuration Guideline