129 should add a start automatic test (#130)

* * Removed references to NULL tests
* Support for "Auto tests" with initialization phase

* * Tested for "Auto tests" with initialization phase
* Updated Janus-Driver to release

* Updated docs

Co-authored-by: Kendar <unknown@kendar.org>

Author: kendarorg

docs/gen_sources/automatictestcalendar.md

@@ -12,7 +12,7 @@
 
 <img src="../images/stimulator_wwwsamplegateway.gif" width="500"/>
 
-* Run the test
+* Run the test with "Play Stimulator"
 * Check the results on the results tab!
 
 
@@ -33,7 +33,7 @@
 
 <img src="../images/verify_structure_script.gif" height="300"/>
 
-* Replay And be happy
+* click "Play Stimulator" And be happy
 * Check the [results](http://www.local.test/plugins/recording/results.html)!
 * Download and save the script as NullAutoTestGateway.json
 
@@ -53,7 +53,7 @@
 [{"id":1,"name":"John","role":"Doe","unexpected":"field"}]
 </pre>
 
-* Run the test again
+* Run the test again with "Play Stimulator"
 * Check the FAILED results! Notice that the field "unexpected" is the one we added!
 
 <img src="../images/unexpected_field.gif" width="500"/>

docs/gen_sources/basic_replaying.md

@@ -11,11 +11,10 @@ is kept to avoid double calls
 
 #### The types
 
-Essentially the replayer has 3 ways to replay
+Essentially the replayer has 2 ways to replay
 
-* Replay: You should invoke the "front" service and HAM will respond to the invocations. You are responsible for running the "initiator calls"
-* Null Infrastructure: Define a Stimulator, the APIs that will guide the test, and (if present) the Stimulated, the APIs that will be invoked by the system under test. Everything is automatically run
-* PACT: Like null, but it invokes the real service and allow the verification of its data and schemas. Everything is automatically run
+* Play: You should invoke the "front" service and HAM will respond to the invocations. You are responsible for running the "initiator calls"
+* Play stimulator: Start to run the stimulator calls (and to respond if not already pressed the play)
 
 At the end of a test the result is shown in a specific page/API
 

docs/gen_sources/manualtestcalendar.md

@@ -16,7 +16,7 @@
 * Stop the "be" application
 * Stop the "gateway" application
 * Download and save the script as NullGateway.json
-* Play the Script
+* Play the Script with "Play"
 * Do the navigation as you did while recording
 * Everything will work as if be is up!
 
@@ -34,6 +34,6 @@
 
 * Stop the "be" application
 * Download and save the script as NullBe.json
-* Play the Script
+* Play the Script clicking on "Play"
 * Do the navigation as you did while recording
 * Everything will work as if gateway is up!

docs/gen_sources/recordcalendardb.md

@@ -86,7 +86,7 @@ set the index 1 (the first to set JDBC prepared statement parameters)
   * Path: /int/
 * "Download" the recording as "DbOnly.json"
 * Now stop the H2 database and the BE application
-* Start replaying the recording
+* Start replaying the recording with "Play"
 * Restart the BE with the be.bat/sh
 * When the initialisation is complete go again of www.sample.test and redo all the steps (John Doe etc)
 * Everything will work :D

docs/generated/automatictestcalendar.md

@@ -111,7 +111,7 @@ You can now check ham application going on http://www.local.test
 
 <img src="../images/stimulator_wwwsamplegateway.gif" width="500"/>
 
-* Run the test
+* Run the test with "Play Stimulator"
 * Check the results on the results tab!
 
 
@@ -132,7 +132,7 @@ You can now check ham application going on http://www.local.test
 
 <img src="../images/verify_structure_script.gif" height="300"/>
 
-* Replay And be happy
+* click "Play Stimulator" And be happy
 * Check the [results](http://www.local.test/plugins/recording/results.html)!
 * Download and save the script as NullAutoTestGateway.json
 
@@ -152,7 +152,7 @@ You can now check ham application going on http://www.local.test
 [{"id":1,"name":"John","role":"Doe","unexpected":"field"}]
 </pre>
 
-* Run the test again
+* Run the test again with "Play Stimulator"
 * Check the FAILED results! Notice that the field "unexpected" is the one we added!
 
 <img src="../images/unexpected_field.gif" width="500"/>

docs/generated/dbtest.md

@@ -155,7 +155,7 @@ set the index 1 (the first to set JDBC prepared statement parameters)
   * Path: /int/
 * "Download" the recording as "DbOnly.json"
 * Now stop the H2 database and the BE application
-* Start replaying the recording
+* Start replaying the recording with "Play"
 * Restart the BE with the be.bat/sh
 * When the initialisation is complete go again of www.sample.test and redo all the steps (John Doe etc)
 * Everything will work :D

docs/generated/manualtestcalendar.md

@@ -114,7 +114,7 @@ You can now check ham application going on http://www.local.test
 * Stop the "be" application
 * Stop the "gateway" application
 * Download and save the script as NullGateway.json
-* Play the Script
+* Play the Script with "Play"
 * Do the navigation as you did while recording
 * Everything will work as if be is up!
 
@@ -132,6 +132,6 @@ You can now check ham application going on http://www.local.test
 
 * Stop the "be" application
 * Download and save the script as NullBe.json
-* Play the Script
+* Play the Script clicking on "Play"
 * Do the navigation as you did while recording
 * Everything will work as if gateway is up!

docs/generated/testcalendar_internals.md

@@ -97,11 +97,10 @@ is kept to avoid double calls
 
 #### The types
 
-Essentially the replayer has 3 ways to replay
+Essentially the replayer has 2 ways to replay
 
-* Replay: You should invoke the "front" service and HAM will respond to the invocations. You are responsible for running the "initiator calls"
-* Null Infrastructure: Define a Stimulator, the APIs that will guide the test, and (if present) the Stimulated, the APIs that will be invoked by the system under test. Everything is automatically run
-* PACT: Like null, but it invokes the real service and allow the verification of its data and schemas. Everything is automatically run
+* Play: You should invoke the "front" service and HAM will respond to the invocations. You are responsible for running the "initiator calls"
+* Play stimulator: Start to run the stimulator calls (and to respond if not already pressed the play)
 
 At the end of a test the result is shown in a specific page/API
 

docs/plugins/replayer/null.md

@@ -10,7 +10,7 @@ reproduced. And you can even verify the data.
 
 An [example](../../generated/automatictestcalendar.md)
 
-Simply push "Play" and you will act as "stimulator" for the application you are verifying
+Simply push "Play stimulator" and you will act as "stimulator" for the application you are verifying
 
 * If you have recorded all the calls made by a UI you could redo all the actions you recorded
 * If you are working with a db and http calls everything recorded will be returned

docs/plugins/replayer/pact.md

@@ -12,7 +12,7 @@
         if(expectedresponse.getStatusCode()!=response.getStatusCode()){
             throw "Expected status code "+expectedresponse.getStatusCode()+" but received "+response.getStatusCode();
         }
-* Run the test!
+* Run the test! with "Play Stimulator"
 
 If (of course) during this kind of test the data changes wildly and changes are propagated
 through requests you can check the [JS Interception](replayer.md) section to use variables