Skip to main content

Python PyPI GH-CI Codecov Apache Ruff

Overview

SAF SDK Testing provides a suite of reusable testing utilities, fixtures, and helper methods designed to standardize and streamline testing across the SAF landscape.

This package centralizes testing utilities for SAF-SDK development. It provides a unified testing infrastructure shared across all SAF-SDK repositories, ensuring consistency and reducing duplication in the development of SAF platform components such as the Desktop Orchestrator, Web Portal, Data Management services, and other core modules.

Core Capabilities

The package is organized into modular components, each addressing specific testing needs:

  • Common Utilities: Shared helper functions for general-purpose testing tasks, including network utilities, directory management, and gRPC certificate handling.

  • Database Testing: Fixtures and methods for testing against PostgreSQL and SQLite databases, including container-managed database instances.

  • Docker Integration: Tools for managing Docker containers and orchestrating containerized test environments.

  • Frontend/Selenium: Selenium WebDriver utilities for end-to-end UI testing, including element waiting strategies and browser interaction helpers.

  • HPS Integration: Testing support for High Performance Computing Services, including deployment processes and stack management.

  • PIM Integration: Utilities for testing Product Instance Management service interactions.

  • Pytest Enhancements: Custom pytest fixtures, markers for platform-specific tests, mocking utilities, and test case documentation helpers.

  • E2E Solution Testing: End-to-end testing infrastructure for SAF solutions, including GLOW engine integration, execution configurations, and project context management.

  • Process Management: Tools for launching and managing external processes during test execution.

Design Principles

This package adheres to strict design principles to ensure reliability and ease of use across the SAF ecosystem:

  • Explicit over implicit: No autouse=True fixtures. Developers must explicitly enable fixtures to maintain clarity about test execution.

  • Simplicity and transparency: Utilities are designed to be easy to understand, allowing developers to predict behavior when calling them.

  • Version-agnostic generality: Utilities are generic and adaptable, avoiding dependencies on specific versions of SAF components.

  • Flat architecture: No nested function or fixture calls, maintaining transparency and predictability in test execution.

  • Backward compatibility: All changes must be backward compatible. Fixes for one repository should never break others.

Installation

Ensure you have all the necessary prerequisites. Then, refer to the installation guidelines for detailed instructions on how to install the project in your system.

Documentation

The official documentation of SAF SDK Testing contains the following chapters:

  • Getting started. This section provides a brief overview and instructions on how to get started with the project. It typically includes information on how to install the project, set up any necessary dependencies, and run a basic example or test to ensure everything is functioning correctly.

  • User guide. The user guide section offers detailed documentation and instructions on how to use the project. It provides comprehensive explanations of the project’s features, functionalities, and configuration options. The user guide aims to help users understand the project’s concepts, best practices, and recommended workflows.

  • Contribute. This section provides guidelines and instructions on how to contribute to the project. It includes information on how to set up the development environment, run tests, submit pull requests, and follow contribution guidelines.

Troubleshooting

For troubleshooting or reporting issues, open an issue in the project repository.

Follow these steps to report an issue:

  • Go to the project repository.

  • Click on the Issues tab.

  • Click on the New Issue button.

  • Provide a clear and detailed description of the issue you are facing.

  • Include any relevant error messages, code snippets, or screenshots.

Additionally, you can refer to the official documentation for additional resources and troubleshooting guides.

License

This project is licensed under the Apache 2.0 License - see the LICENSE file for details.

Changelog

The changelog section provides a summary of notable changes for each version of SAF SDK Testing for Python. It helps you keep track of updates, bug fixes, new features, and improvements made to the project over time.

To view the complete changelog, visit the project repository and navigate to the CHANGELOG file. It provides a comprehensive list of changes categorized by version, along with brief descriptions of each change.

Getting Started

Add to your package’s pyproject.toml:

[tool.poetry.group.tests]
optional = true
[tool.poetry.group.tests.dependencies]
ansys-saf-testing = { version = "^0.1" }
...

Pytest fixtures from ansys-saf-testing are automatically discovered during test collection. No additional fixture registration or plugin configuration is required.

For methods, just import them when needed. Example:

from ansys.saf.testing.selenium import wait_for_element_to_be_clickable, wait_for_partial_text

Extra groups

  • selenium: if you want to use Selenium-related fixtures and methods.

  • hps: if you want to use fixtures and methods for HPS-related testing.

  • docker: if you want to use Docker-related fixtures and methods.

  • pim: if you want to use fixtures and methods for PIM light server testing.

Metadata

Release files for ansys-saf-testing 0.14.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ansys-saf-testing 0.14.0
File Size Uploaded Provenance Actions
ansys_saf_testing-0.14.0.tar.gz 1.3 MB With provenance Details for ansys_saf_testing-0.14.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ansys-saf-testing 0.14.0
File Interpreter ABI Platform Actions
ansys_saf_testing-0.14.0-py3-none-any.whl Python 3 none any Details for ansys_saf_testing-0.14.0-py3-none-any.whl

Total release size: 2.6 MB

Release files / ansys_saf_testing-0.14.0.tar.gz

Download URL ansys_saf_testing-0.14.0.tar.gz
Size 1.3 MB
Tags Source
SHA-256 checksum
How to use checksums
bb40c58da5b7f3f1b3e2df8026c3ad37b401f417a7aa91cb75526449c99e061d
BLAKE2b-256 checksum
How to use checksums
23e99d92000d1ccc6128fed0b86bf27a7666f41adb9fff4f9e670934709a2a0f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.

Transparency log

Release files / ansys_saf_testing-0.14.0-py3-none-any.whl

Download URL ansys_saf_testing-0.14.0-py3-none-any.whl
Size 1.3 MB
Tags Python 3
SHA-256 checksum
How to use checksums
47b7f1d2f0ce2765f1309de3904bd6d329939a64e98dbb7f4c06ff9f50f69b06
BLAKE2b-256 checksum
How to use checksums
0cb3b3a683de17517d2da2f2d3c354365be90ba2cce21b3234c6c2943133e108
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.

Transparency log

Security for ansys-saf-testing 0.14.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for ansys_saf_testing-0.14.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page