[GNUnet-SVN] [taler-merchant] branch master updated: adding chapter about testing the backend

[gnunet]

This is an automated email from the git hooks/post-receive script.

marcello pushed a commit to branch master
in repository merchant.

The following commit(s) were added to refs/heads/master by this push:
     new e23a4e4  adding chapter about testing the backend
e23a4e4 is described below

commit e23a4e4a923898cf1cdcd0f188ec966101140f16
Author: Marcello Stanisci <address@hidden>
AuthorDate: Wed Mar 29 16:08:35 2017 +0200

    adding chapter about testing the backend
---
 doc/manual.texi  | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++-----
 doc/version.texi |  4 ++--
 2 files changed, 60 insertions(+), 7 deletions(-)

diff --git a/doc/manual.texi b/doc/manual.texi
index af2dc37..7636eaf 100644
--- a/doc/manual.texi
+++ b/doc/manual.texi
@@ -55,6 +55,7 @@ Texts.  A copy of the license is included in the section 
entitled
 * Introduction::            Whom this manual is addressed to
 * Installation::            Installing the Merchant backend
 * Configuration::           How to set up the Merchant backend
+* Testing::                 How to test the installed Merchant backend
 * Advanced topics::         Detailed solutions to specific issues
 
 
@@ -740,13 +741,65 @@ reachable.  Production systems should be configured to 
bind
 to a UNIX domain socket or properly restrict access to the
 port.
 
address@hidden Testing
address@hidden Testing
 
address@hidden Add section describing how to test the backend.
address@hidden For this, we should write some tools that make it
address@hidden EASY to test the backend without going through the
address@hidden full manual frontend setup!
address@hidden NOTE: include explaining wallet installation to sysadmin
+The tool @code{taler-merchant-generate-payments} can be used to test
+the merchant backend installation.  It implements all the payment's steps
+in a programmatically way, relying on the backend you give it as input.
+Note that this tool gets installed along all the merchant backend's binaries.
 
+This tool gets configured by a config file, that must have the following
+layout:
+
address@hidden
+[payments-generator]
+
+# The exchange used during the test: make sure the merchant backend
+# being tested accpets this exchange.
+# If the sysadmin wants, she can also install a local exchange
+# and test against it.
+exchange = https://exchange.test.taler.net/
+
+# This value must indicate some URL where the backend
+# to be tested is listening; it doesn't have to be the
+# "official" one, though.
+merchant = http://localbackend/
+
+# This value is used when the tool tries to withdraw coins,
+# and must match the bank used by the exchange. If the test is
+# done against the exchange at https://exchange.test.taler.net/,
+# then this value can be "https://bank.test.taler.net/";.
+bank = https://bank.test.taler.net/
+
+# The merchant instance in charge of serving the payment.
+instance = default
+
+# The currency used during the test. Must match the one used
+# by merchant backend and exchange.
+currency = EUR
address@hidden example
+
+Run the test in the following way:
+
address@hidden
+$ taler-merchant-payments-generator -c config -r
address@hidden example
+
+the argument @code{config} given to @code{-c} points to the configuration
+file and is mandatory; @code{-r} tells the tool to use a remote exchange.
+In case you want to test against a local exchange, remove the @code{-r} option.
+
+If the command terminates with no errors, then the merchant backend is 
correctly
+installed.
+
+After this operation is done, the merchant database will have some dummy
+data in it, so it may be convenient to clean all the tables; to this purpose,
+issue the following command:
+
address@hidden
+$ taler-merchant-dbinit -r
address@hidden example
 
 @node Advanced topics
 @chapter Advanced topics
diff --git a/doc/version.texi b/doc/version.texi
index 0b47203..b89dc6e 100644
--- a/doc/version.texi
+++ b/doc/version.texi
@@ -1,4 +1,4 @@
address@hidden UPDATED 27 January 2017
address@hidden UPDATED-MONTH January 2017
address@hidden UPDATED 29 March 2017
address@hidden UPDATED-MONTH March 2017
 @set EDITION 0.2.0
 @set VERSION 0.2.0

-- 
To stop receiving notification emails like this one, please contact
address@hidden