Skip to content

Commit 9896b2d

Browse files
authored
Merge pull request #307324 from devanshjainms/staf-doc
STAF documentation
2 parents b94a4a0 + 9c3289a commit 9896b2d

8 files changed

Lines changed: 497 additions & 115 deletions
29.2 KB
Loading
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: SAP Testing Automation Framework Architecture
3+
description: Learn about the architecture and components of the SAP Testing Automation Framework
4+
author: devanshjain
5+
ms.author: devanshjain
6+
ms.reviewer: depadia
7+
ms.date: 10/27/2025
8+
ms.service: sap-on-azure
9+
ms.subservice: sap-automation
10+
ms.topic: conceptual
11+
---
12+
13+
# SAP Testing Automation Framework architecture
14+
15+
The SAP Testing Automation Framework uses a distributed architecture with centralized management to orchestrate testing operations across multiple SAP systems.
16+
17+
## Key components
18+
19+
The SAP Testing Automation Framework is built on several core components that work together to provide comprehensive testing capabilities:
20+
21+
- **Management server**: Central orchestration engine and control plane for test operations across all managed SAP systems. The management server coordinates test execution and provides a unified interface for monitoring testing activities.
22+
23+
- **Ansible playbooks**: Automated test execution and system validation orchestration. These playbooks contain the logic for executing different types of tests, including configuration validation, functional tests, and high availability scenarios. The playbooks are integrated with Python modules that provide extended functionality for SAP-specific operations, system monitoring, and data processing. These python modules are designed to be modular and reusable across different framework components.
24+
25+
- **Test scripts**: Helper utilities for test case management and execution. These scripts handle specific testing operations such as critical service failure simulation, network partitioning, and database failover. They're written to be environment and operating system agnostic and can be customized for specific testing requirements.
26+
27+
- **Workspaces**: System-specific configuration and credentials management component. Each workspace contains the necessary configuration files, connection parameters, and authentication details for a specific SAP system or environment. This structure enables the framework to manage multiple systems concurrently while maintaining isolation between environments.
28+
29+
- **Reporting engine**: Generates detailed HTML test reports with comprehensive results, logs, and diagnostic information. The reporting engine provides structured output. It includes test execution summaries, pass/fail status for individual test cases, performance metrics, and detailed error logs for troubleshooting purposes.
30+
31+
## Architecture
32+
33+
### High-level framework structure
34+
35+
The SAP Testing Automation Framework uses a centralized management server architecture that orchestrates all testing scenarios across multiple SAP systems. This orchestrator architecture provides centralized control and efficient resource utilization while maintaining the flexibility to support multiple deployment scenarios.
36+
37+
:::image type="content" source="./media/testing-framework/testing-framework-architecture.png" alt-text="Diagram that shows the SAP Testing Automation Framework architecture.":::
38+
39+
The framework operates on a hub-and-spoke model where the management server acts as the central hub. It coordinates with multiple SAP systems (spokes) to execute tests, collect results, and generate comprehensive reports. Key functions include:
40+
41+
**Test orchestration**: The management server coordinates test suite execution, and ensures proper sequencing of tests across multiple SAP environments.
42+
43+
**Configuration management**: The system maintains directories of configuration templates, system inventories, and customization parameters. These configurations can be applied across environments to ensure uniformity and minimize configuration drift.
44+
45+
**Communication hub**: The server handles secure connections, authentication, and data exchange with target SAP systems, providing a unified interface for all testing operations.
46+
47+
## Next steps
48+
49+
To learn more about specific aspects of the framework:
50+
51+
- For SAP Testing Automation Framework support matrix, see [Understand supported platforms](testing-framework-supportability.md).
52+
- To get started on SAP Testing Automation Framework setup, follow the guide [Setup Guide for SAP Testing Automation Framework](https://github.com/Azure/sap-automation-qa/blob/main/docs/SETUP.MD).
53+
- For running the high availability testing, see [Get started with High Availability testing](testing-framework-high-availability.md).
54+
- For running the configuration checks, see [Get started with configuration validation](https://github.com/Azure/sap-automation-qa/tree/main/docs/CONFIGURATION_CHECKS.md).
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: SAP Testing Automation Framework Configuration Checks
3+
description: Learn about configuration validation checks in the SAP Testing Automation Framework
4+
author: devanshjain
5+
ms.author: devanshjain
6+
ms.reviewer: depadia
7+
ms.topic: reference
8+
ms.service: sap-on-azure
9+
ms.subservice: sap-automation
10+
ms.date: 10/27/2025
11+
ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-content
12+
---
13+
14+
# SAP Testing Automation Framework: Configuration checks (Preview)
15+
16+
The SAP Testing Automation Framework includes comprehensive configuration validation capabilities to ensure SAP systems comply with best practices and guidelines for deployments on Microsoft Azure. These configuration checks help identify potential issues that can affect system performance, reliability, and compliance.
17+
18+
## Overview
19+
20+
Configuration validation is a critical component of the testing framework that performs nonintrusive checks to validate system configurations against SAP on Azure best practices. These checks help identify configuration issues before they affect production systems. The framework validates various aspects of the SAP system, including infrastructure settings, operating system parameters, storage configurations, and cluster resource settings.
21+
22+
These checks are nonintrusive, meaning they don't modify the system or require downtime. Instead, they analyze existing configurations and provide detailed reports highlighting any deviations from recommended practices.
23+
24+
> [!NOTE]
25+
> The configuration checks in SAP Testing Automation Framework is currently in public preview.
26+
27+
### Configuration validation checks
28+
29+
The configuration validation checks within the SAP Testing Automation Framework are systematically organized into distinct logical groupings that provide flexibility in execution. Each group can be executed independently on a standalone basis, or alternatively, all groups can be executed together in a comprehensive validation run.
30+
31+
The primary categories of configuration validation checks include the following. Examples of checks in each category are provided below to illustrate the nature and scope of validations performed:
32+
33+
> [!TIP]
34+
> For the complete and up-to-date list of all configuration checks, refer to the [Configuration Checks documentation](https://github.com/Azure/sap-automation-qa/blob/main/docs/CONFIGURATION_CHECKS.md) on GitHub.
35+
36+
#### Infrastructure
37+
38+
- While not a separate execution category, infrastructure checks are integrated as an essential component within the other categories.
39+
- **Azure Compute**: Validation of Virtual Machine SKU, Accelerated Networking enablement, Availability Set/Zone configuration, and Proximity Placement Group settings.
40+
- **Storage**: Verification of Premium SSD/Ultra Disk usage, Write Accelerator configuration, disk caching policies, and redundancy settings.
41+
42+
#### Database
43+
44+
- Validates SAP HANA or IBM DB2 specific settings.
45+
- **SAP HANA**: Checks for memory allocation, system replication parameters, and Pacemaker cluster configurations (resource agents, fencing mechanisms, and constraints).
46+
- **IBM DB2**: Verification of hardware requirements, system language settings, and operating system tuning parameters.
47+
48+
#### Central services
49+
50+
- Validates the configuration of ASCS (ABAP SAP Central Services) and ERS (Enqueue Replication Server) instances.
51+
- Checks for virtual hostname configuration, file system mount options, and service startup ordering.
52+
53+
#### Application servers
54+
55+
- Validates the configuration of the application server instances.
56+
57+
> [!NOTE]
58+
> High Availability (HA) configuration checks and functional tests are currently supported only for SAP HANA databases. For IBM DB2 databases, only non-HA configuration checks are available.
59+
60+
## Next steps
61+
62+
- To get started on SAP Testing Automation Framework setup, follow the guide [Setup Guide for SAP Testing Automation Framework](https://github.com/Azure/sap-automation-qa/blob/main/docs/SETUP.MD).
63+
- For running the configuration checks, see [Get started with configuration validation](https://github.com/Azure/sap-automation-qa/tree/main/docs/CONFIGURATION_CHECKS.md).
64+
- To understand the architecture of SAP Testing Automation Framework, see [Review the framework architecture](testing-framework-architecture.md).
65+
- For SAP Testing Automation Framework support matrix, see [Understand supported platforms](testing-framework-supportability.md).

0 commit comments

Comments
 (0)