Overview
This example illustrates how pytest can be used within a Guild enabled project.
Project files:
Using pytest
As Guild runs any Python project unmodified, you’re free to use any variety of test frameworks including pytest.
In this example, tests are implemented in the same module containing the test targets: demo.py. You’re free to implement tests however in other ways, including separate modules and packages.
Here’s are tests for the transform function, defined in a function test_transform:
Note the fuzziness of the tests in this case as shown in the last five lines of the function. This highlights a challenge of testing functions that have potentially random effects across systems, even with careful control of random seeds.
You can run tests directly using the pytest command:
pytest demo.py
This command run any functions defined in demo.py that match test_* as tests. pytest prints details messages for any failed tests.
Running tests from Guild
A private operation _check is implemented in guild.yml:
This simply invokes pytest to run the applicable tests for the project.
Note that this approach preserves project functionality: you can still run tests independently of Guild. By using Guild, you can record the results of a test associated with a snapshot of the source code. This is typically a function of CI (continuous integration) tests, which are run from source code commits. This nonetheless shows how simple it is to integrate tests from a another framework into Guild.