sakuli
sakuli copied to clipboard
starter mode "forward-result"
A kind of "quick dry run" which does not really execute something but only sends a small dummy result to each forwarder. Would be very helpful to set up the communication.
Introduce the starter parameter "-cache" which does not execute any suite but only parses $RESULT_JSON (#196) and sends it to the configured forwarders. Alternatively: "-cache filename" In this way, we could also provide a set of default test results (including a dummy screenshot) to check that the forwarders are working properly.
use the cache file as described in #232.
Use additional parameter --delete
to delete the cache file after successful transmission (default: keep).
Copy from #281:
Implement a mode which allows to test a configured forwarder quickly.
Instead of executing sakuli run [suite dir]
one could execute sakuli fwd-test [suite dir]
, which reads the forwarder config from a suite dir without executing the suite.