[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] 02/02: mark up ‘test-auditor.sh’ (two instances)
From: |
gnunet |
Subject: |
[taler-docs] 02/02: mark up ‘test-auditor.sh’ (two instances) |
Date: |
Sat, 12 Dec 2020 07:27:42 +0100 |
This is an automated email from the git hooks/post-receive script.
ttn pushed a commit to branch master
in repository docs.
commit 2d0cbb26a74ce7d85fdaa7c59b6f88d9430f933a
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sat Dec 12 01:25:39 2020 -0500
mark up ‘test-auditor.sh’ (two instances)
---
taler-auditor-manual.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 56f6262..34c2143 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -885,12 +885,12 @@ indicating that the auditor found the inconsistencies.
The script also
verifies that template expansion and LaTeX run work for the JSON output,
but it does not verify the correctness of the final PDF.
-The test-auditor.sh script is written to maximize code coverage: it should
+The ``test-auditor.sh`` script is written to maximize code coverage: it should
cover as many code paths as possible in both the exchange and the auditor. It
should also ideally create all interesting possible variations of the exchange
database fields (within the constraints of the database schema).
-In general, test-auditor.sh runs the tests against an "old" database where
+In general, ``test-auditor.sh`` runs the tests against an "old" database where
some transactions are past the due-date (and hence the aggregator would trigger
wire transfers), as well as a freshly generated exchange database where the
auditor would not perform any transfers. Auditor interactions can be made
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.