saltstack/salt
1
0
Fork 0
mirror of https://github.com/saltstack/salt.git synced 2025-04-17 10:10:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Add bulleted list, and change some other errors

Browse source
This commit is contained in:
MKLeb 2023-09-11 13:32:38 -04:00 • committed by Gareth J. Greenaway
parent 9832840afc
commit 8c67d22d7e
1 changed files with 11 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/topics/packaging/testing.rst
View file

@ -26,12 +26,15 @@ In order to run the package tests, the `relenv
<https://github.com/saltstack/relative-environment-for-python>`_ onedir and
built packages need to be placed in the correct locations.
Place all salt packages for the applicable testing version in
``<repo-root>/pkg/artifacts/``, and the onedir must be located under
``<repo-root>/artifacts/``. Additionally, to ensure complete parity with Salt's
CI/CD suite, place the ``nox`` virtual environment in
``<repo-root>/.nox/test-pkgs-onedir`` The following are a few ways this can be
accomplished easily.
* Place all salt packages for the applicable testing version in
``<repo-root>/pkg/artifacts/``.
* The onedir must be located under ``<repo-root>/artifacts/``.
* Additionally, to ensure complete parity with Salt's CI/CD suite, place the
``nox`` virtual environment in ``<repo-root>/.nox/test-pkgs-onedir``.
The following are a few ways this can be accomplished easily.
You can ensure parity by installing the package test suite through a few
possible methods:
@ -62,7 +65,7 @@ interaction with the salt repo.
The most common use case is to test the packages built on a CI/CD run for a
given PR. To see the possible options for each argument, and other ways to
utilize this command, use the following.
utilize this command, use the following:
.. code-block:: bash
@ -114,8 +117,7 @@ can be performed for artifacts from nightly builds.
Running the tests
=================
You can run the test suite can now be run if all the artifacts are in the
correct location.
You can run the test suite run if all the artifacts are in the correct location.
.. note::