From 0a380c703dfea824ad46a4e028f2d57382264df5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABl=20Madon?= <mael.madon@irit.fr> Date: Wed, 22 Feb 2023 15:58:58 +0100 Subject: [PATCH] doc: small corrections in readme --- test/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/test/README.md b/test/README.md index 2c6acb7..6d094b3 100644 --- a/test/README.md +++ b/test/README.md @@ -33,13 +33,13 @@ pytest interprets all the functions starting with `test_` as tests. For one of t 0. nix-shell puts you into an environment where batsched, batsim, robin, redis, etc. are available (code in [default.nix]) 1. pytest generates combinations of test input (code in [conftest.py]) 2. for each combination of inputs: - 1. pytest generates a [robin] input file - 2. pytest generates batsim and batmen input files if needed - 3. pytest executes [robin] or [robintest] on the generated file + 1. pytest generates a [robin] input file + 2. pytest generates batsim and batmen input files if needed + 3. pytest executes [robin] or [robintest] on the generated file Finally, we have special tests (in the file [test_zexpected_output.py](./test_zexpected_output.py)) verifying that the output of the previous tests correspond to the expected output. -## Running a failed test +## Debugging a failed test You can manually rerun a test with robin: ``` robin test-instances/FAILING-TEST.yaml -- GitLab