How to use getTestMethods method of org.testng.Interface ITestMethodFinder class

If the code you are testing throws an exception, you must handle it in some way. Either by declaring a "throws Exception" in the method signature, or by using try-catch.

If the code you are calling in the method does not throw any exceptions, then you dont need either of those. The compiler will let you know if you need to catch an exception in some way.

Also note that you can do tests that makes sure an exception is thrown, see this answer

1. should i use maven-surefire-plugin and do a heavy cleanup in the test package?
2. is it any way to tell hudson (not in pom.xml of the project being built) to run specific unit tests and ignore others?

If you just want to run unit tests in a single-module project, you can do

mvn test

That will run all maven lifecycle phases up to test, including compile and test-compile (as you can see in built-in lifecycle bindings, the surefire:test goal is executed in phase test). Now if you want to restrict the unit tests that are executed, you can configure the surefire:test plugin execution with the test parameter:

mvn test -Dtest=Funky*Test

(This will execute all test classes that start with Funky and end with Test)

Unfortunately, the command line configuration is limited, if you want multiple includes and excludes you will have to do some XML configuration. I'd suggest to use a dedicated profile for hudson:

<profiles>
    <profile>
        <id>hudson</id>
        <build>
            <plugins>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-surefire-plugin</artifactId>
                    <version>2.6</version>
                    <configuration>
                        <includes>
                            <include>**/TestA.java</include>
                            <include>**/Funky*Test.java</include>
                            <include>**/Test**.java</include>
                        </includes>
                        <excludes>
                            <!-- overrides above include -->
                            <exclude>**/TestButNotMe.java</exclude>
                        </excludes>
                    </configuration>
                </plugin>
            </plugins>
        </build>
    </profile>
</profiles>

Now you can let your hudson call maven like this:

mvn -Phudson test

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

Here is the Answer for your Question:

To avoid loading certain website, you can utilize a feature of Chrome Browser by tweaking the pageLoadStrategy through DesiredCapabilities Class and set it to none as follows:

String ABC = "ABC'S URL";
String chromeDriverPath = "C:\\selenium\\chromedriver.exe" ;
System.out.println("start selenium");
File file = new File(chromeDriverPath);
System.setProperty("webdriver.chrome.driver",file.getAbsolutePath());
ChromeOptions options = new ChromeOptions();
options.addArguments("--start-maximized");
DesiredCapabilities capabilities = DesiredCapabilities.chrome();
capabilities.setCapability(ChromeOptions.CAPABILITY, options);
capabilities.setCapability("pageLoadStrategy", "none");
webDriver driver = new ChromeDriver(capabilities);
driver.get(ABC);

Let me know if this Answers your Question.

Found the answer.

myTestNG.setUseDefaultListeners(false);

You need to have the testng.jar under classpath.

try C:\projectfred> java -cp "path-tojar/testng.jar:path_to_yourtest_classes" org.testng.TestNG testng.xml

Update:

Under linux I ran this command and it would be some thing similar on Windows either

test/bin# java -cp ".:../lib/*" org.testng.TestNG testng.xml

Directory structure:

/bin - All my test packages are under bin including testng.xml
/src - All source files are under src
/lib - All libraries required for the execution of tests are under this.

Once I compile all sources they go under bin directory. So, in the classpath I need to specify contents of bin directory and all the libraries like testng.xml, loggers etc over here. Also copy testng.xml to bin folder if you dont want to specify the full path where the testng.xml is available.

 /bin
    -- testng.xml
    -- testclasses
    -- Properties files if any.
 /lib
    -- testng.jar
    -- log4j.jar

Update:

Go to the folder MyProject and type run the java command like the way shown below:-

java -cp ".: C:\Program Files\jbdevstudio4\studio\plugins\*" org.testng.TestNG testng.xml

I believe the testng.xml file is under C:\Users\me\workspace\MyProject if not please give the full path for testng.xml file

AFAIK, there is no direct way of excluding configuration methods from the testng-results.xml file.

But all said and done, the current entries in the testng-results.xml still lets you distinguish a configuration method from a test method.

For a configuration method there's an extra attribute named is-config="true".

See below for excerpts from your own xml file

<test-method 
    status="PASS" 
    signature="beforeMethod()[pri:0, instance:com.my.test.MyTest@3567135c]" 
    name="beforeMethod" 
    is-config="true" 
    duration-ms="4" 
    started-at="2018-01-22T16:47:46Z" 
    finished-at="2018-01-22T16:47:46Z">
    <reporter-output>
    </reporter-output>
</test-method> <!-- beforeMethod -->

But for a regular @Test method, the attribute is-config=true would not be available.

See below :

<test-method 
    status="PASS" 
    signature="test1()[pri:0, instance:com.my.test.MyTest@3567135c]" 
    name="test1" 
    duration-ms="0" 
    started-at="2018-01-22T16:47:46Z" 
    finished-at="2018-01-22T16:47:46Z">
    <reporter-output>
    </reporter-output>
</test-method> <!-- test1 -->

Would that not help you with your downstream xml processing ?

If that still doesn't work for you, then the other alternatives would include:

• you would build your own version of org.testng.IReporter implementation wherein you construct this xml and then wire it in as a listener.
• You create a package called org.testng.reporters wherein you duplicate the contents of the class org.testng.reporters.XMLReporter into this package, alter the method org.testng.reporters.XMLSuiteResultWriter#getTestResultAttributes to add extra attributes to the method if its not a @Test method.

I've used both, but I have to agree with Justin Standard that you shouldn't really consider rewriting your existing tests to any new format. Regardless of the decision, it is pretty trivial to run both. TestNG strives to be much more configurable than JUnit, but in the end they both work equally well.

TestNG has a neat feature where you can mark tests as a particular group, and then easily run all tests of a specific group, or exclude tests of a particular group. Thus you can mark tests that run slowly as in the "slow" group and then ignore them when you want quick results. A suggestion from their documentation is to mark some subset as "checkin" tests which should be run whenever you check new files in. I never saw such a feature in JUnit, but then again, if you don't have it, you don't REALLY miss it.

For all its claims of high configuration, I did run into a corner case the a couple weeks ago where I couldn't do what I wanted to do... I wish I could remember what it is, but I wanted to bring it up so you know that it's not perfect.

The biggest advantage TestNG has is annotations... which JUnit added in version 4 anyways.

With selenium-java dependency you get all java bindings for all browsers. So, you do not need to change anything in your pom from what you already have. The only thing that would change is your driver initialization code, which is driver = new FirefoxDriver() instead of OperaDriver.