Update versions (Stratio#71)

* runOnEnv versions updated

* Remove setup feature on nightly execution and change login username to Demo (default user)

testsAT/README.md

@@ -21,45 +21,40 @@ mvn verify [-D\<ENV_VAR>=\<VALUE>] [-Dit.test=\<TEST_TO_EXECUTE>|-Dgroups=\<GROU
 Example:
 
 ### Create policies in Gosec
-mvn clean verify -Dgroups=create_policy -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DREGISTERSERVICEOLD=true -DCLUSTER_ID=nightly -DDISCOVERY_POLICIES=true -DlogLevel=DEBUG -DPOSTGRES_VERSION=1.3.0
+mvn clean verify -Dgroups=create_policy -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0 -DREGISTERSERVICEOLD=true -DCLUSTER_ID=nightly -DDISCOVERY_POLICIES=true -DlogLevel=DEBUG -DPOSTGRES_VERSION=1.3.0
 
 ### Install Postgres dependencies
-mvn clean verify -Dgroups=config_postgres -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DCLUSTER_ID=nightly -DlogLevel=DEBUG
+mvn clean verify -Dgroups=config_postgres -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0 -DCLUSTER_ID=nightly -DlogLevel=DEBUG
 
 ### Install Discovery
-mvn clean verify -Dgroups=install_discovery -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DlogLevel=DEBUG
-
-### Setup Discovery
-mvn clean verify -Dgroups=setup_discovery -DDISC_VERSION=0.31.0-ccddeec -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DlogLevel=DEBUG -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov
-## For launch this group it's necessary having deployed next component:
-- docker run -d --name sl selenium/hub:3.9.1 && docker run -d -v /dev/shm:/dev/shm --name docker-selenium-chrome -e HUB_HOST=sl.demo.stratio.com -e HUB_PORT=4444 -e SE_OPTS="-browser browserName=chrome,version=64datagov " selenium/node-chrome-debug:3.9.1
+mvn clean verify -Dgroups=install_discovery -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0 -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DlogLevel=DEBUG
 
 ### Register Postgres database
-mvn clean verify -Dgroups=connection_PG -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DlogLevel=DEBUG -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov
+mvn clean verify -Dgroups=connection_PG -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DDISC_VERSION=0.31.0 -DlogLevel=DEBUG -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov
 ## For launch this group it's necessary having deployed next component:
 - docker run -d --name sl selenium/hub:3.9.1 && docker run -d -v /dev/shm:/dev/shm --name docker-selenium-chrome -e HUB_HOST=sl.demo.stratio.com -e HUB_PORT=4444 -e SE_OPTS="-browser browserName=chrome,version=64datagov " selenium/node-chrome-debug:3.9.1
 
 ### Register Crossdata database
-mvn clean verify -Dgroups=connection_XD -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DlogLevel=DEBUG -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov
+mvn clean verify -Dgroups=connection_XD -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DDISC_VERSION=0.31.0 -DlogLevel=DEBUG -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov
 ## For launch this group it's necessary having deployed next component:
 - docker run -d --name sl selenium/hub:3.9.1 && docker run -d -v /dev/shm:/dev/shm --name docker-selenium-chrome -e HUB_HOST=sl.demo.stratio.com -e HUB_PORT=4444 -e SE_OPTS="-browser browserName=chrome,version=64datagov " selenium/node-chrome-debug:3.9.1
 
 ### Login Tests
-mvn clean verify -Dgroups=login -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly -DDISC_VERSION=0.31.0-ccddeec -DCLUSTER_ID=nightly -DlogLevel=DEBUG -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov -DMODHEADER_PLUGIN=src/test/resources/chromePlugins/ModHeader_v2.2.3.crx -DGROUP_LIST=testadmin,group1 -DUSERNAME=demo -DGROUP=group1 -DADMIN_GROUP=testadmin
+mvn clean verify -Dgroups=login -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly -DDISC_VERSION=0.31.0 -DCLUSTER_ID=nightly -DlogLevel=DEBUG -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov -DMODHEADER_PLUGIN=src/test/resources/chromePlugins/ModHeader_v2.2.3.crx -DGROUP_LIST=testadmin,group1 -DUSERNAME=Demo -DGROUP=group1 -DADMIN_GROUP=testadmin
 ## For launch this group it's necessary having deployed next component:
 - docker run -d --name sl selenium/hub:3.9.1 && docker run -d -v /dev/shm:/dev/shm --name docker-selenium-chrome -e HUB_HOST=sl.demo.stratio.com -e HUB_PORT=4444 -e SE_OPTS="-browser browserName=chrome,version=64datagov " selenium/node-chrome-debug:3.9.1
 
 ### Purge Discovery
-mvn clean verify -Dgroups=purge_discovery -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DlogLevel=DEBUG
+mvn clean verify -Dgroups=purge_discovery -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0 -DlogLevel=DEBUG
 
 ### Delete changes in Postgres
-mvn clean verify -Dgroups=purge_postgres -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DCLUSTER_ID=nightly -DlogLevel=DEBUG
+mvn clean verify -Dgroups=purge_postgres -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0 -DCLUSTER_ID=nightly -DlogLevel=DEBUG
 
 ### Delete policies in Gosec
-mvn clean verify -Dgroups=delete_policy -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DlogLevel=DEBUG -DDISC_VERSION=0.31.0-ccddeec -DREGISTERSERVICEOLD=false -DCLUSTER_ID=nightly -DDISCOVERY_POLICIES=true -DPOSTGRES_VERSION=1.3.0
+mvn clean verify -Dgroups=delete_policy -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DlogLevel=DEBUG -DDISC_VERSION=0.31.0 -DREGISTERSERVICEOLD=false -DCLUSTER_ID=nightly -DDISCOVERY_POLICIES=true -DPOSTGRES_VERSION=1.3.0
 
 ### Nightly
-mvn clean verify -Dgroups=nightly -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0-ccddeec -DREGISTERSERVICEOLD=false -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DCLUSTER_ID=nightly -DDISCOVERY_POLICIES=true -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov -DlogLevel=DEBUG -DPOSTGRES_VERSION=1.3.0
+mvn clean verify -Dgroups=nightly -DBOOTSTRAP_IP=10.200.0.155 -DDCOS_IP=10.200.0.156 -DDCOS_CLI_HOST=dcos-cli-nightly.demo.stratio.com -DDISC_VERSION=0.31.0 -DREGISTERSERVICEOLD=false -DDISCOVERY_SERVICE_VHOST=nightlypublic.labs.stratio.com -DCLUSTER_ID=nightly -DDISCOVERY_POLICIES=true -DSELENIUM_GRID=sl.demo.stratio.com:4444 -DFORCE_BROWSER=chrome_64datagov -DlogLevel=DEBUG -DPOSTGRES_VERSION=1.3.0
 ## For launch this group it's necessary having deployed next component:
 - docker run -d --name sl selenium/hub:3.9.1 && docker run -d -v /dev/shm:/dev/shm --name docker-selenium-chrome -e HUB_HOST=sl.demo.stratio.com -e HUB_PORT=4444 -e SE_OPTS="-browser browserName=chrome,version=64datagov " selenium/node-chrome-debug:3.9.1
 

testsAT/src/test/java/com/stratio/schema/discovery/installation/DISC_nightly_IT.java

@@ -13,7 +13,6 @@
         "src/test/resources/features/001_installation/000_disc_createPolicies.feature",
         "src/test/resources/features/001_installation/001_disc_installPostgres.feature",
         "src/test/resources/features/001_installation/002_disc_installDiscovery.feature",
-        "src/test/resources/features/001_installation/003_disc_setupDiscovery.feature",
         "src/test/resources/features/002_connections/001_disc_connectionPG.feature",
         "src/test/resources/features/002_connections/002_disc_connectionXD.feature",
         //"src/test/resources/features/004_settings/005_disc_loginUser.feature",

testsAT/src/test/resources/features/001_installation/000_disc_createPolicies.feature

@@ -8,7 +8,7 @@ Feature: Create Policy for user crossdata-1 in Gosec
     And I open a ssh connection to '${DCOS_CLI_HOST:-dcos-cli.demo.stratio.com}' with user '${CLI_USER:-root}' and password '${CLI_PASSWORD:-stratio}'
     And I securely send requests to '${DCOS_IP}:443'
 
-  @runOnEnv(DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.30.0)
   @runOnEnv(DISCOVERY_POLICIES=true)
   Scenario: [Create Policy for user crossdata-1 in Gosec][01] Creation policy user crossdata-1
     Given I set sso token using host '${CLUSTER_ID:-nightly}.labs.stratio.com' with user '${DCOS_USER:-admin}' and password '${DCOS_PASSWORD:-1234}' and tenant 'NONE'

testsAT/src/test/resources/features/001_installation/001_disc_installPostgres.feature

@@ -23,7 +23,7 @@ Feature: Install Postgres for Discovery
     And in less than '600' seconds, checking each '20' seconds, I send a 'GET' request to '/service/${POSTGRES_FRAMEWORK_ID_DISC:-postgresdisc}/v1/service/status' so that the response contains '"pg-0002","role":"sync_slave","status":"RUNNING"'
     And in less than '600' seconds, checking each '20' seconds, I send a 'GET' request to '/service/${POSTGRES_FRAMEWORK_ID_DISC:-postgresdisc}/v1/service/status' so that the response contains '"pg-0003","role":"async_slave","status":"RUNNING"'
 
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Basic Installation Postgres Dependencies][01] Check PostgresTLS
     Given I open a ssh connection to '${DCOS_CLI_HOST:-dcos-cli.demo.stratio.com}' with user '${CLI_USER:-root}' and password '${CLI_PASSWORD:-stratio}'
     Then in less than '600' seconds, checking each '20' seconds, the command output 'dcos task | grep ^${POSTGRES_FRAMEWORK_ID_TLS:-postgrestls} | grep R | wc -l' contains '1'
@@ -71,7 +71,7 @@ Feature: Install Postgres for Discovery
     When I run 'docker exec -t !{postgresDocker} psql -p !{pgPortCalico} -U postgres -c "CREATE ROLE \"${DISCOVERY_TENANT_NAME:-crossdata-1}\" with password '${DISCOVERY_DATASTORE_PASSWORD:-stratio}' SUPERUSER CREATEDB CREATEROLE REPLICATION BYPASSRLS LOGIN"' in the ssh connection
     Then the command output contains 'CREATE ROLE'
 
-  @runOnEnv(DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.30.0)
   Scenario: [Basic Installation Postgres Dependencies][02] Create database for Discovery on Postgrestls
     Given I set sso token using host '${CLUSTER_ID:-nightly}.labs.stratio.com' with user '${DCOS_USER:-admin}' and password '${DCOS_PASSWORD:-1234}' and tenant 'NONE'
     And I securely send requests to '${CLUSTER_ID:-nightly}.labs.stratio.com:443'
@@ -106,7 +106,7 @@ Feature: Install Postgres for Discovery
     Then the command output contains 'CREATE DATABASE'
     Then I close database connection
 
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Basic Installation Postgres Dependencies][04] Create data for Discovery on PostgresTLS
     Given I open a ssh connection to '!{pgIP}' with user '${CLI_USER:-root}' and password '${CLI_PASSWORD:-stratio}'
     And I outbound copy 'src/test/resources/schemas/createPGContent.sql' through a ssh connection to '/tmp'

testsAT/src/test/resources/features/001_installation/002_disc_installDiscovery.feature

@@ -16,22 +16,22 @@ Feature: Install Discovery for Discovery
     And I save element in position '0' in '$.status[?(@.role == "master")].ports[0]' in environment variable 'postgresMD5_Port'
     And I wait '5' seconds
 
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Basic Installation Discovery][02] Obtain postgreSQL ip and port
     Given I send a 'GET' request to '/service/${POSTGRES_FRAMEWORK_ID_TLS:-postgrestls}/v1/service/status'
     Then the service response status must be '200'
     And I save element in position '0' in '$.status[?(@.role == "master")].dnsHostname' in environment variable 'postgresTLS_Host'
     And I save element in position '0' in '$.status[?(@.role == "master")].ports[0]' in environment variable 'postgresTLS_Port'
     And I wait '5' seconds
 
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Basic Installation Discovery][03] Check Crossdata is running
     Given I run 'dcos marathon task list ${DISCOVERY_TENANT_NAME:-crossdata-1} | awk '{print $5}' | grep ${DISCOVERY_TENANT_NAME:-crossdata-1}' in the ssh connection and save the value in environment variable 'crossdataTaskId'
     Then in less than '300' seconds, checking each '10' seconds, the command output 'dcos marathon task show !{crossdataTaskId} | grep '"state": "TASK_RUNNING"' | wc -l' contains '1'
     Then in less than '300' seconds, checking each '10' seconds, the command output 'dcos marathon task show !{crossdataTaskId} | grep 'healthCheckResults' | wc -l' contains '1'
     Then in less than '300' seconds, checking each '10' seconds, the command output 'dcos marathon task show !{crossdataTaskId} | grep '"alive": true' | wc -l' contains '2'
 
-  @runOnEnv(DISC_VERSION=0.28.9||DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.28.9)
   Scenario: [Basic Installation Discovery][04] Create config file
     Given I create file 'config_discovery_${DISC_VERSION}.json' based on 'schemas/config_discovery_0.28.9.json' as 'json' with:
       | $.Service.cpus                        | REPLACE | ${DISCOVERY_SERVICE_CPUS:-1}                                             | number  |
@@ -63,7 +63,7 @@ Feature: Install Discovery for Discovery
       | $.Datastore.host                      | UPDATE  | !{postgresMD5_IP}                                                        | n/a     |
       | $.Datastore.port                      | REPLACE | !{postgresMD5_Port}                                                      | number  |
 
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Basic Installation Discovery][05] Modify info to connect to postgrestls
     Given I create file 'config_discovery_${DISC_VERSION}.json' based on 'config_discovery_${DISC_VERSION}.json' as 'json' with:
       | $.Service.folder                                             | ADD     | ${DISCOVERY_SERVICE_FOLDER:-discovery}                                 | string  |
@@ -101,7 +101,7 @@ Feature: Install Discovery for Discovery
     Given I run 'dcos marathon task list ${DISCOVERY_SERVICE_NAME:-discovery} | awk '{print $5}' | grep ${DISCOVERY_SERVICE_NAME:-discovery}' in the ssh connection and save the value in environment variable 'discoveryTaskId'
     Then in less than '300' seconds, checking each '10' seconds, the command output 'dcos marathon task show !{discoveryTaskId} | grep TASK_RUNNING | wc -l' contains '1'
 
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Basic Installation Discovery][07] Check Discovery installation
     Given in less than '300' seconds, checking each '10' seconds, the command output 'dcos marathon task list ${DISCOVERY_SERVICE_FOLDER:-discovery}/${DISCOVERY_SERVICE_NAME:-discovery} | awk '{print $5}' | grep ${DISCOVERY_SERVICE_NAME:-discovery} | wc -l' contains '1'
     And I run 'dcos marathon task list ${DISCOVERY_SERVICE_FOLDER:-discovery}/${DISCOVERY_SERVICE_NAME:-discovery} | awk '{print $5}' | grep ${DISCOVERY_SERVICE_NAME:-discovery}' in the ssh connection and save the value in environment variable 'discoveryTaskId'

testsAT/src/test/resources/features/001_installation/003_disc_setupDiscovery.feature

@@ -1,7 +1,7 @@
 Feature: Setup Discovery
 
   @web
-  @runOnEnv(DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION=0.31.0)
   Scenario: Setup discovery
     Given My app is running in '${DISCOVERY_SERVICE_VHOST:-nightlypublic.labs.stratio.com}:443'
     When I securely browse to '${DISCOVERY_DISCOVERY_PATH:-/discovery}'

testsAT/src/test/resources/features/002_connections/001_disc_connectionPG.feature

@@ -6,7 +6,7 @@ Feature: Connection on Postgres
     And I open a ssh connection to '${DCOS_CLI_HOST:-dcos-cli.demo.stratio.com}' with user '${CLI_USER:-root}' and password '${CLI_PASSWORD:-stratio}'
     And I securely send requests to '${DCOS_IP}:443'
 
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Connection Postgres][01] Obtain postgreSQL ip and port
     Given I send a 'GET' request to '/service/${POSTGRES_FRAMEWORK_ID_TLS:-postgrestls}/v1/service/status'
     Then the service response status must be '200'
@@ -15,7 +15,7 @@ Feature: Connection on Postgres
     And I wait '5' seconds
 
   @web
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Connection Postgres][02] Register postgres database
     Given My app is running in '${DISCOVERY_SERVICE_VHOST:-nightlypublic.labs.stratio.com}:443'
     When I securely browse to '${DISCOVERY_DISCOVERY_PATH:-/discovery}'
@@ -42,7 +42,7 @@ Feature: Connection on Postgres
 
   @ignore @manual
   @web
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Connection Postgres][03] Get postgres database id
     Given My app is running in '${DISCOVERY_SERVICE_VHOST:-nightlypublic.labs.stratio.com}:443'
     When I securely browse to '${DISCOVERY_DISCOVERY_PATH:-/discovery}'
@@ -65,7 +65,7 @@ Feature: Connection on Postgres
 
   @ignore @manual
   @web
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Connection Postgres][04] Check query postgres database
     Given My app is running in '${DISCOVERY_SERVICE_VHOST:-nightlypublic.labs.stratio.com}:443'
     When I securely browse to '${DISCOVERY_DISCOVERY_PATH:-/discovery}'

testsAT/src/test/resources/features/002_connections/002_disc_connectionXD.feature

@@ -7,7 +7,7 @@ Feature: Connection on XData
     And I securely send requests to '${DCOS_IP}:443'
 
   @web
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Connection XData][02] Register xdata database
     Given My app is running in '${DISCOVERY_SERVICE_VHOST:-nightlypublic.labs.stratio.com}:443'
     When I securely browse to '${DISCOVERY_DISCOVERY_PATH:-/discovery}'
@@ -35,7 +35,7 @@ Feature: Connection on XData
 
   @ignore @manual
   @web
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Connection Postgres][03] Get xdata database id
     Given My app is running in '${DISCOVERY_SERVICE_VHOST:-nightlypublic.labs.stratio.com}:443'
     When I securely browse to '${DISCOVERY_DISCOVERY_PATH:-/discovery}'
@@ -58,7 +58,7 @@ Feature: Connection on XData
 
   @ignore @manual
   @web
-  @runOnEnv(DISC_VERSION=0.29.0||DISC_VERSION=0.30.0||DISC_VERSION=0.31.0-ccddeec)
+  @runOnEnv(DISC_VERSION>0.29.0)
   Scenario: [Connection Postgres][04] Check query xdata database
     Given My app is running in '${DISCOVERY_SERVICE_VHOST:-nightlypublic.labs.stratio.com}:443'
     When I securely browse to '${DISCOVERY_DISCOVERY_PATH:-/discovery}'

testsAT/src/test/resources/features/003_login/004_disc_loginWithHeaders.feature

@@ -23,7 +23,7 @@ Feature: Login with headers
     And '0' elements exists with 'xpath://h2[contains(.,'notexists')]'
 
   Scenario: Set PROXY_HEADERS variable to existing user and non-existing group (user: demo (or USERNAME variable), group: notexists)
-    When We update system property 'PROXY_HEADERS' to value 'vnd.bbva.user-id:${USERNAME:-demo},vnd.bbva.group-id:test'
+    When We update system property 'PROXY_HEADERS' to value 'vnd.bbva.user-id:${USERNAME:-Demo},vnd.bbva.group-id:test'
 
   @web
   Scenario: Login through headers - User exists --> AUTOMATIC LOGIN