adding print statements to check the test flow

ProjectEKA · Oct 14, 2020 · ff35cd5 · ff35cd5
1 parent 2b7799e
commit ff35cd5
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/pom.xml b/pom.xml
@@ -7,6 +7,7 @@
     <artifactId>ProjectEKA-tets</artifactId>
     <version>1.0-SNAPSHOT</version>
     <properties>
+        <java.version>11</java.version>
         <maven.compiler.source>11</maven.compiler.source>
         <maven.compiler.target>11</maven.compiler.target>
         <testng.version>6.9.8</testng.version>
@@ -122,6 +123,9 @@
                         </execution>
                     </executions>
                     <configuration>
+                        <includes>
+                            <include>src/**/java/**/**/*.java</include>
+                        </includes>
                         <linkXRef>true</linkXRef>
                         <rulesets>
                             <ruleset>${pmd-ruleset-path}</ruleset>

diff --git a/src/test/java/tests/mobiletests/utils/RunnerFactory.java b/src/test/java/tests/mobiletests/utils/RunnerFactory.java
@@ -8,6 +8,8 @@ public class RunnerFactory {
   public static IRunner runner;
 
   public void instantiateRunner(AppiumDriver driver) {
+    System.out.println("ENVIRONMENT ---> " + System.getenv("env"));
+    System.out.println("DRIVER ---> " + driver.getClass().getName());
     String env = System.getenv("env");
     switch (env) {
       case "ncg":