salt/tests/pytests
Alexander Graul dcfe24fed7 state.apply: don't check for cached pillar errors
state.apply request new pillar data from the server. This done to always
have the most up-to-date pillar to work with. Previously, checking for
pillar errors looked at both the new pillar and the in-memory pillar.
The latter might contain pillar rendering errors even if the former does
not.

For this reason, only the new pillar should be checked, not both.
2022-10-06 13:27:19 -06:00
..
functional Adding more functional tests for MySQL state module 2022-10-05 06:47:32 -06:00
integration state.apply: don't check for cached pillar errors 2022-10-06 13:27:19 -06:00
scenarios Update to isort 5.10.1 2022-08-01 12:49:16 -06:00
unit state.apply: don't check for cached pillar errors 2022-10-06 13:27:19 -06:00
__init__.py Pyupgrade and drop six 2021-07-06 09:04:28 -04:00
conftest.py Update to isort 5.10.1 2022-08-01 12:49:16 -06:00
README.md

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 directoy shall become the top level tests directoy.