How to use EmailableReporter class of org.testng.reporters package

There's no problem with TestNG per se here.

The dataproviderthreadcount attribute that you have set in your pom file is going to be applicable and relevant only when you are running your test via mvn clean test.

If you are trying to run this test class from within the IDE (IntelliJ or Eclipse for that matter) its not going take affect.

Here's a test class that I created which is powered by a data provider ( For the sake of simplicity I have intentionally kept cucumber out of the equation )

import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;

public class AppTest {

  @Test(dataProvider = "dp")
  public void shouldAnswerWithTrue(int i) {
    System.err.println("Running on [" + Thread.currentThread().getId() + "]");

  }

  @DataProvider(name = "dp", parallel = true)
  public Object[][] testData() {
    return new Object[][]{
        {1},
        {2},
        {3},
        {4},
        {5},
        {6}
    };
  }
}

Here's the command line output when I run mvn clean test

[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ testng_playground ---
[INFO] 
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.rationaleemotions.AppTest
Running on [15]
Running on [14]
Running on [15]
Running on [14]
Running on [14]
Running on [15]
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.62 s - in com.rationaleemotions.AppTest
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0

You can't. In Java there is no concept of a subpackage, so odp.proj and odp.proj.test are completely separate packages.

Testng is calling methods in this specific order: serviceData, beforeMethod and m1.

If you want to pass a mock with a data provider, you have to create it before or into the data provider method.

This version of tapestry-hibernate is not available in the maven central repository neither in Apache staging repository (you refer to it in your POM file).

If you want to go with the beta version then I suggest you to take the latest available (for example this one).

EDIT:

in the end of your POM file you have a property:

<tapestry-release-version>5.4-beta-24</tapestry-release-version>

change it to:

<tapestry-release-version>5.4-beta-28</tapestry-release-version>

EDIT2:

BTW, you define the following dependency twice:

<dependency>
    <groupId>org.apache.tapestry</groupId>
    <artifactId>tapestry-hibernate</artifactId>
    <version>${tapestry-release-version}</version>
</dependency>

which does no harm at the moment but you'd better clean it up.

If all your tests extend this class, you could just put this into a static initializer. This will only be executed once (when the class is loaded).

public class AbstractPamTest
{
  protected static final String user;
  protected static final String passwd;
  protected static final String badPasswd;

  static
  {
      user = System.getProperty("test.login");
      passwd = System.getProperty("test.passwd");
      if (user == null || passwd == null)
          throw new IllegalStateException("Please define test.login and"
              + " test.passwd before running tests");
      badPasswd = passwd + "x";
  }
}

Or put it in a completely different class, that is used/called by classes that need the password/user. You won't need to extend the AbstractPamTest then. Additionally you should provide getters/setter there, so that you can change user/password at runtime, if one testcase needs different values.

  private  static String user;
  private  static String passwd;
  private  static String badPasswd;

  static
  {
      user = System.getProperty("test.login");
      passwd = System.getProperty("test.passwd");
      if (user == null || passwd == null)
          throw new IllegalStateException("Please define test.login and"
              + " test.passwd before running tests");
      badPasswd = passwd + "x";
  }

  public static String getUser()
  {
    return user;
  }

  public static void setUser(String pUser)
  {
    user = pUser;
  }

  public static String getPasswd()
  {
    return passwd;
  }

  public static void setPasswd(String pPasswd)
  {
    passwd = pPasswd;
  }

You can create a rule class for your initialization:

public class Resource extends ExternalResource {
    protected void before() {
        // ...
    }

    protected void after() {
        // ...
    }
}

and then reference it in each test:

@ClassRule public static Resource resource = new Resource();

Any per-test customisation can be done by making resource an anonymous inner class and overriding methods, or passing parameters to its constructor.

If you have a common base class, you can put resource in there, and then only declare it in subclasses that need to customize it. In junit, class rules in subclasses will override class rules in a parent class with the same name.

The error is:

Caused by: java.lang.SecurityException: sealing violation: can't seal package com.sun.media.imageioimpl.plugins.jpeg2000: already loaded
    at java.net.URLClassLoader.getAndVerifyPackage(Unknown Source)

So that means you try to seal already loaded package. That package is in a file like jai_imageio-*.jar. Check if you have two similar jars and remove one of them.

The problem is with how your initialising the webdriver instance. The below code snippet

@BeforeTest
@Parameters({"browser", "baseURL"})
public void setUp(@Optional String browser, @Optional String baseURL) {
    driver = getBrowserType(browser);
    driver.manage().timeouts().implicitlyWait(20, TimeUnit.SECONDS);
    driver.manage().window().maximize();
    driver.navigate().to(baseURL);
}

causes the setUp method to be invoked only once per <test> tag because its part of a common base class to both your test classes.

So if there are two test classes in your <test> tag such as

<test name="chromeTest" >
    <parameter name="browser" value="chrome"></parameter>
    <classes>
        <class name="tests.HomePageTest"></class>
        <class name="tests.NavigationMenuTest"></class>
    </classes>
</test>

then the setUp method would get invoked only for HomePageTest and be skipped when executing NavigationMenuTest

That explains why you see a NullPointerException for your second test class within the <test> tag. You would need to change this by perhaps annotating the setUp method with @BeforeClass instead of @BeforeTest

The correct usage of including plugin dependencies is as follows, you can merge the plugin dependencies at a single place -

<build>
    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.6.0</version>
                <configuration>
                    <source>1.8</source>
                    <target>1.8</target>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.19.1</version>
                <configuration>
                    <suiteXmlFiles>
                        <suiteXmlFile>testng.xml</suiteXmlFile>
                    </suiteXmlFiles>
                    <skipTests>true</skipTests>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-jar-plugin</artifactId>
                <version>2.3.2</version>
            <!--Notice I have removed the configs here. Not required to generate the jar-->
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-resources-plugin</artifactId>
                <version>3.0.1</version>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.shared</groupId>
                <artifactId>maven-invoker</artifactId>
                <version>2.2</version>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-shade-plugin</artifactId>
                <version>2.4.3</version>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

Further you can edit the respective plugin configs within the same declaration.

Also for using maven-shade-plugin and maven-jar-plugin, you might want to look into the samples here and here respectively.