Tobias Schneck
Tobias Schneck
add the examples to Sakuli CI build so that all docker examples will be executed after a checkin
* enable as alternative web-test-framework selenium * Make possible to extend existing Selenium tests * Maybe refactor in this step also the Java DSL
check in detail if we can find another solution to solve the issue #219. Maybe patch sahi. To get into the error check the stacktraces when the retry happens. Projekt...
since #219 is done, check if we can reduce the timeout of 150s: Sahi code in lib.js row: 145 `this.maxCycles = ScriptRunner.getMaxCyclesForPageLoad() + 300;` Properties to check: ``` script.time_between_steps=100 script.max_cycles_for_page_load=1200...
implement after #310 * Use [Sweetest Model](https://gitlab.consol.de/testautomatisierung/sweetest/tree/master/sweetest-api/src/main/java/org/sweetest/api/model) for all twig based Forwarder as data model. * separate Forwarder in independent modules * Basic Forwarder Module * Gearman Forwarder * Check_MK...
Add sing-up to: * README.md overview page * doc: general
https://labs.consol.de/sakuli/install/ Introduce new folder structure: ``` versions/snapshots/ versions/vX.X.X/ -zip -jar stable -> versions/..../ dev -> versions/...snapshot ``` Maybe use a CSS to get a more modern view
Create some latest stable tags for the different configs of the omd images `consol/omd-labs-XXX-sakuli`
In sahi v4 it was necessary to implement a delay for syncron status calls from the browser side javascript part, see property `sahi.proxy.requestDelayOnSikuliInput.delayTime`. Due to the upgrade to sahi5, see...
**PROBLEM:** Sometimes Sakuli prints out after all is down the following log line ERROR [2018-03-07 19:19:27.543] - Connection refused (Connection refused) This comes from the Sahi `ShutDownHookl` class. When `System.exit()`...