salt/tests/pytests
Georg Pfuetzenreuter 24a58e8211
Some checks failed
CI / Prepare Workflow Run (push) Has been cancelled
CI / Pre-Commit (push) Has been cancelled
CI / Lint (push) Has been cancelled
CI / NSIS Tests (push) Has been cancelled
CI / Prepare Release: (push) Has been cancelled
CI / Documentation (push) Has been cancelled
CI / Build Source Tarball (push) Has been cancelled
CI / Build Onedir Dependencies (push) Has been cancelled
CI / Build Salt Onedir (push) Has been cancelled
CI / Build Packages (push) Has been cancelled
CI / CI Deps (push) Has been cancelled
CI / Test Package (push) Has been cancelled
CI / Test Salt (push) Has been cancelled
CI / Combine Code Coverage (push) Has been cancelled
CI / Set the Pipeline Exit Status (push) Has been cancelled
Set virtual grain in Podman systemd container
Correctly handle the systemd-detect-virt output to identify a Podman
container running systemd as what it is instead of as a physical machine.

Signed-off-by: Georg Pfuetzenreuter <georg.pfuetzenreuter@suse.com>
2025-02-26 14:04:01 -07:00
..
functional Correct dictionary format returned in test 2025-02-10 15:26:36 -07:00
integration Add regression test for #66562 2025-02-12 16:58:48 -07:00
pkg Update various out-dated links, emails, etc. 2025-01-11 15:25:01 -07:00
scenarios Fix flaky multi-master test 2025-02-12 16:58:48 -07:00
unit Set virtual grain in Podman systemd container 2025-02-26 14:04:01 -07:00
__init__.py
conftest.py Fix publish_signing_algorithm conditional 2024-06-18 22:12:20 -07:00
README.md Fix broken backport 64229 form master to 3006.x 2023-05-26 07:30:29 +01:00

New Test Suite

Welcome to the new test suite for Salt!

Any test under this directory shall be written exploring the full capabilities of PyTest. That means, no occurrences of the TestCase class shall be used, neither our customizations to it.

Purpose

While PyTest can happily run unittest tests(withough taking advantage of most of PyTest's strengths), this new path in the tests directory was created to provide a clear separation between the two approaches to writing tests. Some(hopefully all) of the existing unittest tests might get ported to PyTest's style of writing tests, new tests should be added under this directory tree, and, in the long run, this directory shall become the top level tests directory.