Many unnecesary or barely used files were removed for clarity

src/main/resources/META-INF/maven/archetype-metadata.xml

@@ -38,17 +38,10 @@
                 <include>*.java</include>
             </includes>
         </fileSet>
-        <fileSet filtered="true" encoding="UTF-8">
-            <directory>src/test/java/__groupId__/__artifactId__/utils</directory>
-            <includes>
-                <include>BaseTest.java</include>
-            </includes>
-        </fileSet>
         <fileSet filtered="true" encoding="UTF-8">
             <directory>src/test/resources</directory>
             <includes>
                 <include>features/*.feature</include>
-                <include>schemas/*.conf</include>
                 <include>schemas/*.json</include>
             </includes>
         </fileSet>

src/main/resources/archetype-resources/src/test/java/__groupId__/__artifactId__/glue/CustomStepsDefinition.java

@@ -22,8 +22,7 @@ public class CustomStepsDefinition extends BaseGSpec {
     RestSpec restSpec;
 
     /**
-     * Example of how to inherit the needed objects from GingerSpec. For more information
-     * check https://github.com/veepee-oss/gingerspec/wiki/Creating-your-own-steps
+     * Example of how to inherit the needed objects from GingerSpec.
      * @param spec the CommonGSpec class
      */
     public CustomStepsDefinition(CommonG spec) {
@@ -37,7 +36,6 @@ public CustomStepsDefinition(CommonG spec) {
         restSpec = new RestSpec(this.commonspec);
     }
 
-
     /**
      * This is an example of how to create your own selenium steps. For more info check
      * https://github.com/veepee-oss/gingerspec/wiki/Creating-your-own-steps#selenium-example
@@ -58,7 +56,6 @@ public void myCustomSeleniumStep() throws InterruptedException {
         driver.findElement(By.id("submit")).click();
     }
 
-
     /**
      * This is an example of how to create your own REST steps. You can directly use
      * REST-Assured for this (https://rest-assured.io/). For more information, check

src/main/resources/archetype-resources/src/test/java/__groupId__/__artifactId__/runners/CucumberRunnerIT.java

@@ -1,14 +1,17 @@
 package ${groupId}.${artifactId}.runners;
 
 import io.cucumber.testng.CucumberOptions;
-import ${groupId}.${artifactId}.utils.BaseTest;
+import com.privalia.qa.utils.BaseGTest;
 
 
 /**
  * This is the runner class responsible of running the included *.feature files in the project.
  * Glue files can be specified in the {@link CucumberOptions} annotation
  *
- * Also check out the {@link BaseTest} class, there you can create TestNG hooks and more :)
+ * Here you can also create your own TestNG hooks or even configure parallel tests execution.
+ * For more info on these topics check:
+ * https://testng.org/doc/documentation-main.html#annotations
+ * https://cucumber.io/docs/guides/parallel-execution/#testng
  */
 @CucumberOptions(plugin = {
                 "json:target/CucumberRunnerIT.json",
@@ -19,7 +22,7 @@
                 "src/test/resources/features"
         },
         glue = "classpath:${groupId}.${artifactId}.glue")
-public class CucumberRunnerIT extends BaseTest {
+public class CucumberRunnerIT extends BaseGTest {
 
 
 }

src/main/resources/archetype-resources/src/test/resources/configuration/common.properties

@@ -1,23 +1,10 @@
 # ********************************* COMMON PROPERTIES ************************************************
 # This file is used to store variables that you can use directly in your Scenarios and Steps. For this
-# you will have to use ${envProperties:my.key}. For example, the following step:
+# you will have to use ${envProperties:my.key}. Ideally, this is used to store variables that can change
+# depending on an environment (like urls, user credentials, IP addresses, etc).
 #
-#       Given I put some '${envProperties:spice.name}' in my soup
-#
-# Will be transformed to:
-#
-#       Given I put some 'ginger' in my soup
-#
-# For using the variables in the other files, you have to use -Denv=<filename> when running your test,
-# for example:
-#
-# mvn verify -Denv=int      -> uses the variables from int.properties file
-# mvn verify -Denv=uat      -> uses the variables from uat.properties file
-# mvn verify -Denv=pro      -> you got the idea, right?
-#
-# Ideally, this is used to store variables that can change depending on an environment (like urls,
-# user credentials, IP addresses, etc). If -Denv is not detected, the values from this file will be
-# used by default
+# Take a look at the full documentation here
+# https://github.com/veepee-oss/gingerspec/wiki/Gherkin-variables#using-environment-dependent-variables
 #*****************************************************************************************************
 
 spice.name=ginger

src/main/resources/archetype-resources/src/test/resources/configuration/preprod.properties

@@ -0,0 +1,10 @@
+# ********************************* INT PROPERTIES ************************************************
+# This file is used to store variables that you can use directly in your Scenarios and Steps. For this
+# you will have to use ${envProperties:my.key}. Ideally, this is used to store variables that can change
+# depending on an environment (like urls, user credentials, IP addresses, etc).
+#
+# Take a look at the full documentation here
+# https://github.com/veepee-oss/gingerspec/wiki/Gherkin-variables#using-environment-dependent-variables
+#*****************************************************************************************************
+
+spice.name=celery