aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorErik Skultety <eskultet@redhat.com>2022-07-14 12:24:50 +0200
committerErik Skultety <eskultet@redhat.com>2022-07-14 15:14:19 +0200
commitdb0d56034bdff66bb346726893638da6cc1423fb (patch)
tree930f9d92d3099ffd33a4838763ef7c550352bfeb /docs
parentc7ee5c353b177910140ccd4ecb46e721443c2c68 (diff)
downloadlibvirt-ci-db0d56034bdff66bb346726893638da6cc1423fb.zip
libvirt-ci-db0d56034bdff66bb346726893638da6cc1423fb.tar.gz
libvirt-ci-db0d56034bdff66bb346726893638da6cc1423fb.tar.bz2
docs: testing: Mention to be cautious about using --regenerate-output
If the proposed changes also include changes to e.g. Dockerfile generator potential regressions could not be caught by the test suite if --regenerate-output is always used. Signed-off-by: Erik Skultety <eskultet@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/testing.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/testing.rst b/docs/testing.rst
index ef4ac15..425dce6 100644
--- a/docs/testing.rst
+++ b/docs/testing.rst
@@ -13,4 +13,6 @@ suite as
$ python3 -m pytest --regenerate-output
and the expected package data sets will be updated. You can then just grab the
-changes and add them to your commit.
+changes and add them to your commit. Beware though that if you test a buggy
+code this way the tests would not be able to catch regressions since the
+"correct" test output would now match the flawed output.