How to use onFinish method of org.testng.Interface ISuiteListener class

A simple if statement seems to work pretty well too:

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = {"classpath:test-context.xml"})
public class myTest {

    public static boolean dbInit = false;

    @Autowired
    DbUtils dbUtils;

    @Before
    public void setUp(){

        if(!dbInit){

            dbUtils.dropTables();
            dbUtils.createTables();
            dbInit = true;

        }
    }

 ...

Close and restart your IDE and use following .xml:

 <suite name="Suite" verbose="1">
<test name="Test1">

    <groups>
        <run>

        <exclude name="Car" />
        </run>
    </groups>
    <classes>

        <class name="example.Dependent" />
        <class name="example.Vehicle" />


    </classes>

</test>


 </suite> 

Here's how you do it. TestNG lets you inject an Object[] array into the @BeforeMethod annotated method. When TestNG sees an object array, it natively injects the parameters that are about to be passed to a data driven @Test method. Refer this TestNG wiki page to learn more about what are all allowed by TestNG as part of native injection.

Here's how your base class can look like :

import org.testng.annotations.BeforeMethod;

public class AbstractBaseClass {
    @BeforeMethod
    public void beforeMethod(Object[] parameters) {
        //Here we are assuming that the testname will always be the first parameter
        //in the 1D array that gets sent for every iteration of @Test method
        if (parameters != null && parameters.length >= 1) {
            String testname = parameters[0].toString();
            System.out.println("Test name obtained in beforeMethod() " + testname);
        }
    }
}

And here's how your test class can look like

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

public class TestClass extends AbstractBaseClass {
    @Test(dataProvider = "getData")
    public void testMethod(String testname, int count) {
        Assert.assertNotNull(testname);
        Assert.assertTrue(count > 0);
    }

    @DataProvider
    public Object[][] getData() {
        return new Object[][]{
                {"LoginTestCase", 100},
                {"ComposeMailTestcase", 200}
        };
    }
}

This way you can get hold of your test name in your base class itself, even if its being fed in via a data provider.

And as always please ensure you are on TestNG 6.11 (which as of today July 20, 2017 is the latest released version of TestNG)

Create an testng.xml file say name as testsuite.xml.

Now follow below 2 steps:

Step 1: Create an batch file for scheduler:

use below code - modify it and paste in notepad. save the notepad in working directory as"run.bat"

set ProjectPath=C:\Selenium\Selenium_tests\DemoProject 
echo %ProjectPath%
set classpath=%ProjectPath%\bin;%ProjectPath%\Lib\*
echo %classpath%
java org.testng.TestNG %ProjectPath%\testsuite.xml

• a) First line is for setting project path .

• b) second line is for verifying that path is set or not.

• c) third line is for setting classpath - lib folder contain all the jar file added to project build path

• d) fourth line is for verifying whether classpath is set or not

• e) fifth line is for executing xml file having details of all test.

Step 2:

• Go to control panel.

• Administrative tool.

• Task scheduler and create a task which will trigger run.bat file at the time you want.

It will work.

Most testing frameworks (the xUnit family) are based on the JUnit framework. The Assert family of functions in JUnit have the (expected, actual) format; it became a convention, and most of the other frameworks followed that convention.

Some frameworks (like TestNG or NUnit 2.4+ for .NET) reversed that order (with the use of a constraint-based model for NUnit) to increase readability ("make sure that the actual value is 56" feels more natural than "make sure that 56 is the actual value").

The bottom line is: stick to the convention of your framework. If you use JUnit, put the expected value first. If you use TestNG, put the actual value first. You're right, that makes no difference in the test results when you accidentally reverse the arguments. But it makes a big difference in the default message you get from a failing test. When your reversed assertEquals(ShouldBeTrueButReturnsFalse(), true) in JUnit fails, the default message says "expected [false] but found [true]", where it should have said "expected [true] but found [false]". This is confusing, to say the least, and you shouldn't have to deal with a possible misdirection of that message.

Some of the unit tests in the Github link you provide don't follow the convention and have the same problem. Don't do that. Stick to the convention of your framework.

XStream!

Updated: I added unmarshal part as requested in comments..

import com.thoughtworks.xstream.XStream;
import com.thoughtworks.xstream.converters.Converter;
import com.thoughtworks.xstream.converters.MarshallingContext;
import com.thoughtworks.xstream.converters.UnmarshallingContext;
import com.thoughtworks.xstream.io.HierarchicalStreamReader;
import com.thoughtworks.xstream.io.HierarchicalStreamWriter;

import java.util.AbstractMap;
import java.util.HashMap;
import java.util.Map;

public class Test {

    public static void main(String[] args) {

        Map<String,String> map = new HashMap<String,String>();
        map.put("name","chris");
        map.put("island","faranga");

        XStream magicApi = new XStream();
        magicApi.registerConverter(new MapEntryConverter());
        magicApi.alias("root", Map.class);

        String xml = magicApi.toXML(map);
        System.out.println("Result of tweaked XStream toXml()");
        System.out.println(xml);

        Map<String, String> extractedMap = (Map<String, String>) magicApi.fromXML(xml);
        assert extractedMap.get("name").equals("chris");
        assert extractedMap.get("island").equals("faranga");

    }

    public static class MapEntryConverter implements Converter {

        public boolean canConvert(Class clazz) {
            return AbstractMap.class.isAssignableFrom(clazz);
        }

        public void marshal(Object value, HierarchicalStreamWriter writer, MarshallingContext context) {

            AbstractMap map = (AbstractMap) value;
            for (Object obj : map.entrySet()) {
                Map.Entry entry = (Map.Entry) obj;
                writer.startNode(entry.getKey().toString());
                Object val = entry.getValue();
                if ( null != val ) {
                    writer.setValue(val.toString());
                }
                writer.endNode();
            }

        }

        public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {

            Map<String, String> map = new HashMap<String, String>();

            while(reader.hasMoreChildren()) {
                reader.moveDown();

                String key = reader.getNodeName(); // nodeName aka element's name
                String value = reader.getValue();
                map.put(key, value);

                reader.moveUp();
            }

            return map;
        }

    }

}

I also got the same exception:

I tried the following steps:

1. In Eclipse> Project > Clean. (The Exception remained)

2. I ran another project(The testng.xml ran successfully)

After running another project, I ran the project in which I was getting the Exception, and fortunately it worked for me, with no errors.

This can be added to the test.

@IfProfileValue(name="test-profile", value="IntegrationTest")
public class PendingChangesITCase extends AbstractControllerIntegrationTest {
    ...
}

To select the tests to be executed just add the value to the profile for executing the integration tests.

<properties>
    <test-profile>IntegrationTest</test-profile>
</properties>

If the maven profile selected does not have the property value, it will not execute the integration tests.

To quote TestNG's documentation:

Any @AfterMethod method can declare a parameter of type ITestResult, which will reflect the result of the test method that was just run.

You can use this parameter to check if the test succeeded or not:

@AfterMethod(groups = { "Regression" })
public void afterMethod(ITestResult result) {
   if (result.getStatus() == ITestResult.SUCCESS) {
        // Setting driver used to false as this test case is pass
        driverUsed.put("supportDriver", false);
        System.out.println("Test case is pass");
   }
}