Community
Participate
Working Groups
As far as I can see, the command line tool 'testexec' ignores the step-delay configured in a test suite. HTML-AUT (web application). Manually run a test suite - the step delay works as desired. Depending on the web application under test and the QA employee, the configured delay can be up to 2 seconds. Running a test suite automatically - the execution is too fast and fails.
Created attachment 224358 [details] Fix the bug by moving setStepDelay() to class TestExecution The bug has been reproduced and fixed by moving the method setStepDelay() from the gui-class TestExecutionContributor to the command-line-class TestExecution. Now the step delay is used both in the gui and by the testexec command line. As an example a developer test has been made with the following arguments: testexec -server localhost -port 60035 -autconfig WebAUT@localhost -dburl "jdbc:h2:~/.jubula/database/embedded;MVCC=TRUE;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE" -dbuser sa -dbpw "" -project TestProject -version 1.0 -language de_DE -resultdir /.../WebAUTWorkingDirectory/result -datadir /.../WebAUTWorkingDirectory/data -testsuite NewTestSuite -timeout 25000
The patch has been reviewed and applied with changeset http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=dc2d73e691346692f3815dc245a3a2bba2f0e530
Fix verified, I tested this using the SA tests in our Samples project using TS 1.1_SIMPLE_ADDER_TEST_WITH_TEST_STEPS and 3.2_SIMPLE_ADDER_HTML_TEST_MULTI_DATA_SETS with AUTs SA Swing and SA HTML and changed the step delay several times. Closing this ticket.