gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-anastasis] branch master updated: test fix


From: gnunet
Subject: [taler-anastasis] branch master updated: test fix
Date: Tue, 09 Jun 2020 16:02:58 +0200

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

ds-meister pushed a commit to branch master
in repository anastasis.

The following commit(s) were added to refs/heads/master by this push:
     new 5385ccb   test fix
5385ccb is described below

commit 5385ccb487416997a8e1813545b00925aeab033f
Author: Dominik Meister <dominiksamuel.meister@students.bfh.ch>
AuthorDate: Tue Jun 9 16:02:54 2020 +0200

     test fix
---
 doc/thesis/implementation.tex | 44 ++++++++++++++++++++-----------------------
 1 file changed, 20 insertions(+), 24 deletions(-)

diff --git a/doc/thesis/implementation.tex b/doc/thesis/implementation.tex
index 012c975..a4a3e6d 100644
--- a/doc/thesis/implementation.tex
+++ b/doc/thesis/implementation.tex
@@ -397,31 +397,27 @@ and Free Software.~\cite{libmicrohttpd}
 \subsection{Testing}
 
 To test our application, we used the GNU Taler testing library as our
-foundation for some of our testings.  This library allows you to create 
testing instances of
+foundation for t of our testings.  This library allows you to create testing 
instances of
 both the Anastasis application and the GNU Taler payment system. We
-implemented unit tests for the crypto functions and the simple HTTP REST. A
-simplified test flow would be the following:
+implemented unit tests for the crypto functions and the database operations.
+The following four tests are independently performed.
 
-\begin{enumerate}
-\item The testing library starts an instance of the Anastasis server
-  and a GNU Taler merchant and exchange service.
-\item The Anastasis server will connect to a test database only used
-  for testing.
-\item The testing library first sets up the database and tests if it
-  can create records.
+\begin{itemize}
+\item The first test is the database test. The Anastasis testing library first 
connects to a test database, this database is only used for the testing, we 
never test on the live database. The test first deletes and recreates the 
database. After that it will perform several unit tests to check if the 
database queries of the application are working as intended.
 \item Next we test the Anastasis crypto API, it tests all the
-  cryptographic functions used in the API. The most important part is
-  that the recreation of the keys and decryption works as intended.
+cryptographic functions used in the API with unit tests.
+The most important part is  that the recreation of the keys 
+and decryption works as intended.
 \item After the basic parts of the application are tested the client
-  will test every request in the Anastasis server API. It will check
-  if the server responds the intended way and if the status codes are
-  correct.
-\item At the end the whole application flow is tested, the testing
-  library will first perform a secret split and then a secret
-  recovery. It tests if the core functionality of the application
-  works and if the secret is recovered correctly.
-\end{enumerate}
-% FIXME: the above does not seem accurate;
-% unit tests for crypto and simple HTTP REST
-% tests do not necessarily preceede the
-% integration tests done with the testing library!
+will test every request in the Anastasis server API. For this we need the
+Taler Testing library. The Taler testing library will start an instance
+of the Anastasis webserver and a GNU Taler merchant service. The merchant
+service is needed to proccess the payment operations. The testing library
+will now send a request to every end point of the Anastasis REST API. It will
+check if every response of the REST API is as intended.
+\item At the end the whole application flow is tested. For this
+we need to start a Anastasis server, Taler merchant and Taler exchange 
instance. 
+The library will now perform a full secret split and secret recovery.
+This test is successful if the provided core secret at the begin, matches the
+recovered core secret. 
+\end{itemize}
\ No newline at end of file

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]