How to use getInvocationTimeOut method of org.testng.Interface ITestNGMethod class

Indeed you will need a custom converter for this as it is two nested collection which you do not want to show and those objects might have other child elements which would be serialized.

This is a case not directly covered by XStream, but easily fixed with a custom converter.

You can find all this in a git clone of your project which contains all those modifications. But as everything should be visible here, I subsequently explain the key portions to the question including some code examples.

I implemented such a converter for your project. The code doing the conversion is this:

  @Override
  public void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {
    TestRow test = (TestRow)source;
    for (TestArguments arg : test.getArguments()) {
      for (ArgObject val : arg.getAllTestArguments()) {
        writer.startNode(val.getKey());
        writer.addAttribute("type", val.getType());
        writer.setValue(val.getVal());
        writer.endNode();

      }
    }
  }

  @Override
  public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {
    TestArguments testargs = new TestArguments();
    while (reader.hasMoreChildren()) {
      reader.moveDown();
      String typeval = reader.getAttribute("type");
      if (typeval.isEmpty()) {
        typeval = "null";
      }
      testargs.getAllTestArguments().add(new ArgObject(reader.getNodeName(), typeval, reader.getValue()));
      reader.moveUp();
    }
    TestRow result = new TestRow(testargs);
    return result;
  }

This will serialize all ArgObjects to xml with the flat node structure you defined in your ArgConverter. The deserialization creates the object back from this data.

You had two bugs in your source code which prevented deserialization:

• XStream deserialization does not recognize all alias Annotations. It had problems with your root element SuiteData (aliased to suite). For this I added a aliad to the XStream object like this xStream.alias("suite", SuiteData.class); in your XMLDataHelper.
• If you create a TestArguments instance with a default constructor (as you'll have to through deserialization), you call reset which assigns your argsWrapper member to null which then makes adding arguments quite impossible. I fixed that be newly initializing that member variable in the reset method (argsWrapper = new ArrayList<ArgObject>();).

As far as I understand your code this works as expected for serialization / deserialization. I wrote a small test program to force this process in each way and it seems to produce the same result:

public class XMLDataHelperTest {

  public static void main(String[] args) {
    File file = new File(System.getProperty("user.dir"), "test.xml");
    if (file.isFile()) {
      assertTrue(file.delete());
    }

    // write it once
    XMLDataHelper helper = new XMLDataHelper(file.getAbsolutePath());

    // read it once
    helper = new XMLDataHelper(file.getAbsolutePath());
    System.out.println(file);
  }
}

Had the same problem as you. Zero results in TestNG reports but looks like tests were runned. Finally get this work on two separate executions of maven-surefire-plugin

1. First remove the dependencies section from plugin.
   • otherwise if you use <testNGArtifactName> (and we'll need it) tests will be executed by TestNG anyway and will fail on java.lang.NullPointerException
2. Have some separation of TestNG tests and JUnit tests. In our case NG test class names ends with TestNg
3. skip default execution
4. define two <executions> like below:

<plugin>
    <!-- configured to work with JUnit and TestNg in same project separatelly -->
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>              
    <configuration>
        <!-- whatever you need... -->
        <!-- skip the default execution, we have separate for Ng and for JUnit -->
        <skip>true</skip>
    </configuration>
    <executions>
        <execution>
            <id>TestNg-execution</id>
            <phase>test</phase>
            <goals>
                <goal>test</goal>
            </goals>
            <configuration>
                <!-- overwrite skip from default config -->
                <skip>false</skip>
                <includes>
                    <include>%regex[.*TestNg.*]</include>
                </includes>
                <!-- used to skip JUnit profider -->
                <junitArtifactName>dev:null</junitArtifactName>
                <!-- to continue on next execution in case of failures here -->
                <testFailureIgnore>true</testFailureIgnore>
            </configuration>
        </execution>
        <execution>
            <id>JUnit-execution</id>
            <phase>test</phase>
            <goals>
                <goal>test</goal>
            </goals>
            <configuration>

                <skip>false</skip>
                <!-- used to skip TestNg profider -->
                <testNGArtifactName>dev:null</testNGArtifactName>
                <excludes>
                    <exclude>%regex[.*TestNg.*]</exclude>                               
                </excludes>
            </configuration>                    
        </execution>
    </executions>
</plugin>

Tested with:

<junit-version>4.11</junit-version>
<maven-surefire-plugin-version>2.16</maven-surefire-plugin-version>
<org.testng-version>6.8.7</org.testng-version>

This configuration is the marge of ideas from:
Running TestNG-, JUnit3- and JUnit4-tests with Maven Surefire in one run,
your SUREFIRE bug report,
surefire plugin configuration

Hope it helps.

Easiest solution would be, add the below lines in surefire plugin.

<suiteXmlFiles>
    <!-- pass testng.xml files as argument from command line -->
    <suiteXmlFile>${suiteXmlFile}</suiteXmlFile>
</suiteXmlFiles>

And run your xml file as below,

mvn clean test -Dsurefire.suiteXmlFiles=/path/to/testng.xml

Running the following code:

public class SolicitudEmpleo extends LaunchBrowser{
    private String campoDni;
    private String firstName;
    private String lastName;

    @Factory (dataProvider="dataProviderMethod")
    public SolicitudEmpleo(String campoDni, String firstName, String lastName){
        this.campoDni=campoDni;
        this.firstName = firstName;
        this.lastName = lastName;
        System.out.println("data number"+campoDni);
    }

    @DataProvider
    public static Object[][] dataProviderMethod() {
        return new Object[][] { {"000007", "Bill", "Gates"}, {"000008", "Stack", "Overflow"} };
    }
    @Test (priority = 1)
    public void testCase1(){
        System.out.println("Test 1");  
    }
    @Test (priority = 2)
    public void testCase2() throws InterruptedException { 
        System.out.println("Test 2 "+campoDni);
    }
    @Test (priority = 3)
    public void testCase3() throws InterruptedException {
        System.out.println("Test 3 "+firstName+","+lastName);
    }
    @Test (priority = 4)
    public void testCase4() throws InterruptedException {
        System.out.println("Test 4");
    }   
}
public class LaunchBrowser {
    @BeforeSuite()
    public void launchBrowser() throws InterruptedException {
        System.out.println("Launching");
    }
}

Produces the following output:

data number000007
data number000008
Launching
Test 1
Test 1
Test 2 000007
Test 2 000008
Test 3 Bill,Gates
Test 3 Stack,Overflow
Test 4
Test 4

Therefore, the problem is not with TestNG. It must be something with WebDriver, and probably the site you are using.

Just delete the automatically created TestNG Run/Debug Configuration (Run | Edit Configurations... action) in Run Configurations dialog for the project. Then you will again have the option to choose test framework.

UPD: Since 2017.3 version there is suggest.all.run.configurations.from.context property which you can set (Help | Edit Custom Properties action) to true, then IDE will show you all the configurations that are available for current context.

TestNG or any other testing tool decides success or failure of a test based on assertion.

Assert.assertEquals(actualVal, expectedVal);

So if actualVal and expectedVal are same then test will pass else it will fail.

Similarly you will find other assertion options if you using any IDE like Eclipse.

Go to Preferences > Editor > File and Code Templates and choose JUnit4 Test Method. This by default has the form of

@org.junit.Test
public void test${NAME}() {
  ${BODY}
}

Change to

@org.junit.Test
public void should${NAME}() {
  ${BODY}
}

You have to implement ISuiteLisnter like below:

public ISuiteListener implements ISuiteLisnter {

 private long testCount = 0 ; 
 private List<ITestNGMethod> testMethods = null;

 public void setTestCount(long testCount){
      this.testCount = testCount;
 }

 public long getTestCount(){
     return this.testCount;
 }

 @Override
 public void onStart( ISuite suite){
       testMethods  = suite.getAllMethods();
       this.testCount = testMethods.size();
 }

 @Override 
 public void onFinish( ISuite suite){

 }
}

This will give you count of all the test methods in suite which is currently running along this you can look around utility method which is present in ITestNGMethod to process.

Have you tried using Reporter.log()? (it's part of the TestNG API)