Before we updated to gauge Version 0.8.4 we never set any flag for the execution order. But since update the execution order of the specifications seems to be random.
Now I set the flag like that:
gauge "--tags="install|restrictedmode"" ./specs --verbose --order=sort
And hoped that now the execution would be alphabetical again. But unfortunately it is a random order and every run is different, no mattter if the order flag is set or not.
We intentionally added numbers at the beginning of the specification name, but this does not seem to work anyway. How can I get a non random execution order again?
Expected behavior
alphabetical execution of specifications
Actual behavior
random execution of specifications
Steps to reproduce
- run gauge with gauge "--tags="install|restrictedmode"" ./specs --verbose --order=sort
- for this tag there are three specifications found: 001 Engage installation, 005 Restricted mode, 007 Reschedule Jobs
- This specifications should be executed in the following order
001 Engage installation
005 Restricted mode
007 Reschedule Jobs
- But they are executed like this:
Gauge version
Gauge version: 0.8.4
Plugins
html-report (4.0.0)
java (0.6.3)
`
[go] Task: gauge "--tags="install|restrictedmode"" ./specs --verbose --order=sort
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2017-05-22 15:38:55,932 0 [Thread-1] INFO com.infoniqa.engage.utils.BrowserFactory - looking for sahi user data under path: C:\GoAgent\pipelines\engage-gauge-demo\engage.gauge\sahi\userdata
Mai 22, 2017 3:38:55 PM net.sf.sahi.config.Configuration reinitialize
INFORMATION: Sahi properties file = C:\dev\sahi_pro\config\sahi.properties
Mai 22, 2017 3:38:55 PM net.sf.sahi.config.Configuration reinitialize
INFORMATION: Sahi user properties file = C:\GoAgent\pipelines\engage-gauge-demo\engage.gauge\sahi\userdata\config\userdata.properties
2017-05-22 15:38:56,603 671 [Thread-1] DEBUG com.infoniqa.engage.utils.BrowserFactory - start wait for proxy
2017-05-22 15:38:56,603 671 [Thread-1] INFO com.infoniqa.engage.utils.BrowserFactory - try waiting for sahi proxy
Mai 22, 2017 3:38:56 PM java.util.prefs.WindowsPreferences
WARNUNG: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
Mai 22, 2017 3:38:57 PM java.util.logging.LogManager$RootLogger log
INFORMATION: VALID LICENSE
Sahi Pro 1-User License
Licensed to: Infoniqa HR Solutions GmbH
Issued date: 21 Sep 2016
Expiry date: 21 Sep 2017
2017-05-22 15:38:57,774 1842 [Thread-1] INFO com.infoniqa.engage.utils.BrowserFactory - sahi proxy is not yet started
2017-05-22 15:38:57,785 1853 [Thread-1] INFO com.infoniqa.engage.utils.BrowserFactory - try waiting for sahi proxy
Sahi Pro v6.3.2 started. Listening on port: 9999
Configure your browser to use this server and port as its proxy
Browse any page and CTRL-ALT-DblClick on the page to bring up the Sahi Controller
Mai 22, 2017 3:38:58 PM net.sf.sahi.util.BrowserTypesLoader loadAvailableBrowserTypes
INFORMATION:
Reading browser types from: C:\GoAgent\pipelines\engage-gauge-demo\engage.gauge\sahi\userdata\config\browser_types.xml
Mai 22, 2017 3:38:58 PM net.sf.sahi.util.Utils setUrlConnectionFollowRedirectsInternal
INFORMATION: urlConnectionFollowRedirectsInternal = false
Mai 22, 2017 3:38:58 PM in.co.sahi.datastore.SahiDB
INFORMATION: Using Database:
driverName=org.h2.Driver
jdbcurl=jdbc:h2:C:/GoAgent/pipelines/engage-gauge-demo/engage.gauge/sahi/userdata/database/db0;AUTO_SERVER=TRUE;DB_CLOSE_DELAY=-1;IGNORECASE=TRUE
userName=sa
Using Connection Pool
2017-05-22 15:38:58,674 2742 [Thread-1] DEBUG com.infoniqa.engage.utils.BrowserFactory - finished wait for proxy in 2070 ms
2017-05-22 15:38:58,814 2882 [Thread-1] INFO com.infoniqa.engage.utils.BrowserFactory - Launch browser chrome
Mai 22, 2017 3:38:58 PM in.co.sahi.distributed.BrowserType launchInstanceCommon
INFORMATION: Acquired available browser instance after retries:0 threadNo:0
sessionId:sahi_4e0e6f1c011ae04db50840e01e45a0c8b9f9
Mai 22, 2017 3:38:58 PM in.co.sahi.datastore.SahiDB createTables
INFORMATION: Check tables version
Mai 22, 2017 3:38:59 PM net.sf.sahi.test.ProcessHelper execute
INFORMATION: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --user-data-dir=C:/GoAgent/pipelines/engage-gauge-demo/engage.gauge/sahi/userdata\browser\chrome\profiles\sahi0 --proxy-server=localhost:9999 --disable-popup-blocking --always-authorize-plugins --allow-outdated-plugins --enable-npapi --incognito "http://sahi.example.com/s/dyn/Driver_start?sahisid=sahi_4e0e6f1c011ae04db50840e01e45a0c8b9f9__SahiAmpersandSahi__startUrl=http%3A%2F%2Fsahi.example.com%2F_s_%2Fdyn%2FDriver_initialized%3FstartUrl%3D"
Mai 22, 2017 3:38:59 PM in.co.sahi.datastore.SahiDB createTables
INFORMATION: versionFromDB=2016-10-13 14:21:30
Mai 22, 2017 3:38:59 PM in.co.sahi.datastore.SahiDB createTables
INFORMATION: version=2016-10-13 14:21:30
Mai 22, 2017 3:38:59 PM in.co.sahi.datastore.SahiDB createTables
INFORMATION: At current version. No changes were done.
Mai 22, 2017 3:38:59 PM in.co.sahi.datastore.SahiDB createTables
INFORMATION: {result: [["SAHIKEY","SAHIVALUE"],["dbVersion","83"],["versionNo","2016-10-13 14:21:30"]]}
Mai 22, 2017 3:38:59 PM in.co.sahi.datastore.SahiDB createTables
INFORMATION: Finished preparing report tables: 513ms
001 Engage installation
001 Engage installation Mai 22, 2017 3:39:00 PM net.sf.sahi.test.ProcessHelper$PIDGatherer run
INFORMATION: PIDs: [1272, 4796, 3396, 2076]; 1998 ms
P2017-05-22 15:39:09,967 14035 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - getUpdateLink
2017-05-22 15:39:09,968 14036 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - link: updatePending.goToAdminLink.message
2017-05-22 15:39:10,484 14552 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - link: zur engage Update Administrationsseite.
2017-05-22 15:39:11,100 15168 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - link: the engage Update Administration site.
2017-05-22 15:39:11,619 15687 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - update link exists: false
2017-05-22 15:39:12,244 16312 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - no engage! update necessary
P2017-05-22 15:39:12,248 16316 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - wait for installation to be ready
2017-05-22 15:39:12,248 16316 [Thread-1] INFO com.infoniqa.common.acceptance.EngageInstallation - installation done!
P P P2017-05-22 15:39:33,736 37804 [Thread-1] INFO com.infoniqa.engage.login.LoginScreen - User INFONIQA SUPERADMIN is logged IN.
P
007 Reschedule Jobs
007 Reschedule Jobs P P P P P P
005 Restricted mode
005 Change System Settings P P P
Mai 22, 2017 3:40:07 PM net.sf.sahi.test.ProcessHelper kill
INFORMATION: Kill: [1272, 4796, 3396, 2076]
Successfully generated html-report to => C:\GoAgent\pipelines\engage-gauge-demo\engage.gauge\reports\html-report
Specifications: 3 executed 3 passed 0 failed 0 skipped
Scenarios: 3 executed 3 passed 0 failed 0 skipped
Total time taken: 1m12.601s
`
So what should I do to get the execution order alphabetically again?
thanks in advance.
Regards,
Natalie