diff --git a/tests/domaincapstest.c b/tests/domaincapstest.c
index 97b306f652..f88f330f60 100644
--- a/tests/domaincapstest.c
+++ b/tests/domaincapstest.c
@@ -483,9 +483,8 @@ mymain(void)
      * Run "tests/qemucapsprobe /path/to/qemu/binary >foo.replies"
      * to generate updated or new *.replies data files.
      *
-     * If you manually edit replies files you can run
-     * VIR_TEST_REGENERATE_OUTPUT=1 tests/qemucapabilitiesnumbering
-     * to fix the replies ids.
+     * If you manually edit replies files or want to edit them programmaticaly
+     * use scripts/qemu-replies-tool --regenerate
      *
      * Once a replies file has been generated and tweaked if necessary,
      * you can drop it into tests/qemucapabilitiesdata/ (with a sensible
diff --git a/tests/qemucapabilitiesdata/README.rst b/tests/qemucapabilitiesdata/README.rst
index eea07048e9..90e240f800 100644
--- a/tests/qemucapabilitiesdata/README.rst
+++ b/tests/qemucapabilitiesdata/README.rst
@@ -109,12 +109,10 @@ file on a code change causing a change to the actual QMP query process.
 
 In such case a careful manual modification of the ``.replies`` is tolerated.
 
-To aid such modification the tool ``tests/qemucapabilitiesnumbering`` can be
+To aid such modification the tool ``scripts/qemu-replies-tool.py`` can be
 used.
 
 The tool validates and updates the numbering of the entries in the QMP dump in
 case something was modified.
 
 The tool also allows programatic modification of the ``.replies`` file.
-
-See ``tests/qemucapabilitiesnumbering.c``.