From: Paul Floyd Date: Sat, 18 May 2024 13:39:34 +0000 (+0200) Subject: README_DEVELOPERS: better to generate stdout expecteds directly from test exes X-Git-Tag: VALGRIND_3_24_0~134 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=5050749df0c2be3ad4331a2d33359ff1d89c72f4;p=thirdparty%2Fvalgrind.git README_DEVELOPERS: better to generate stdout expecteds directly from test exes --- diff --git a/README_DEVELOPERS b/README_DEVELOPERS index a13b35574..71581bd86 100644 --- a/README_DEVELOPERS +++ b/README_DEVELOPERS @@ -141,7 +141,13 @@ The easiest way to generate the expected files is to run the test. Create empty files with touch (otherwise the test won't run) then run the test from the top directory using perl and vg_regtest script (as in the "Running the regression tests" section. Then copy "tool/tests/newtest.stderr.out" to -"tool/tests/newtest.stderr.exp". Do the same for the .stderr.exp file. +"tool/tests/newtest.stderr.exp". It is better to generate the .stdout.exp +file directly from the testcase. You can do that by redirecting stdout to +the expected file, for instance (in the test directory) + ./newtest arg1 arg2 > newtest.stdout.exp +This is not always possible - sometimes there are tests that depend on the use +of client requests or have imperfect emulation of opcodes. +Make sure that the test runs and passes. The last file to change is .gitignore in the top directory. Add a new entry, for example "/tool/tests/newtest".