Merge pull request #110 from mdelapenya/enrich-test-names

chore: enrich test names

Author: mdelapenya

e2e/features/metricbeat/apache.feature

@@ -1,6 +1,6 @@
 Feature: As a Metricbeat developer I want to check that the Apache module works as expected
 
-Scenario Outline: Check module is sending metrics to Elasticsearch without errors
+Scenario Outline: Check Apache-<apache_version> is sending metrics to Elasticsearch without errors
   Given Apache "<apache_version>" is running for metricbeat
     And metricbeat is installed and configured for Apache module
     And metricbeat waits "20" seconds for the service

e2e/features/metricbeat/mysql.feature

@@ -1,6 +1,6 @@
 Feature: As a Metricbeat developer I want to check that the MySQL module works as expected
 
-Scenario Outline: Check module is sending metrics to Elasticsearch without errors
+Scenario Outline: Check <variant>-<version> is sending metrics to Elasticsearch without errors
   Given "<variant>" v<version>, variant of "MySQL", is running for metricbeat
     And metricbeat is installed and configured for "<variant>", variant of the "MySQL" module
     And metricbeat waits "20" seconds for the service

e2e/features/metricbeat/redis.feature

@@ -1,7 +1,7 @@
 @redis
 Feature: As a Metricbeat developer I want to check that the Redis module works as expected
 
-Scenario Outline: Check module is sending metrics to Elasticsearch without errors
+Scenario Outline: Check Redis-<redis_version> is sending metrics to Elasticsearch without errors
   Given Redis "<redis_version>" is running for metricbeat
     And metricbeat is installed and configured for Redis module
     And metricbeat waits "20" seconds for the service

e2e/features/metricbeat/vsphere.feature

@@ -1,6 +1,6 @@
 Feature: As a Metricbeat developer I want to check that the vSphere module works as expected
 
-Scenario Outline: Check module is sending metrics to Elasticsearch without errors
+Scenario Outline: Check vSphere-<vsphere_version> is sending metrics to Elasticsearch without errors
   Given vSphere "<vsphere_version>" is running for metricbeat
     And metricbeat is installed and configured for vSphere module
     And metricbeat waits "120" seconds for the service