How to use hashCode method of org.testng.xml.XmlDefine class

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

Does your TestClass or any of its superclasses have a @Test annotation on it? If a class has such an annotation, all public methods are considered test methods.

If you are not too particular about using JUnit, then you can use TestNG framework. They have multi threaded support.

I found the reason ..Test class and controller class are named in the same package path...

The solution is as follows:

@ContextConfiguration(classes = {ScanResultConfigureController.class})
@ComponentScan(
        includeFilters = {
                @ComponentScan.Filter(type = FilterType.CUSTOM,
                        value = {ScanResultConfigureController.class})
        },
        useDefaultFilters = false,
        lazyInit = true
)

It was a stupid noob mistake indeed. We are using a multi-project setup with a master project and several folders on the same level, which contain the code and the tests. The build.gradle I was using accidentally only configured the master project to use TestNG. The solution is to include the test target within the allprojects or subprojects closure. Which is explained here: What is the difference between allprojects and subprojects

So here is the working build.gradle:

def mainClassName = 'nl.xillio.contentplatform.view.Run'


// Load settings for all projects including master and subprojects
allprojects {
    apply plugin: 'java'
    apply plugin: 'eclipse'

    version '0.1'

    repositories {
        mavenCentral()
        maven {
            url 'http://mvnrepository.com/maven2'
        }
        maven {
            url 'http://download.java.net/maven/2'
        }
    }
}

// Load the dependencies for all subprojects (layers)
subprojects {
    dependencies {
    //to do: move these to the correct subprojects
        compile 'javax.inject:javax.inject:1'
        compile 'org.springframework:spring-context:4.1.4.RELEASE'
        compile 'org.springframework:spring-core:4.1.4.RELEASE'
        compile 'org.springframework:spring-beans:4.1.4.RELEASE'
        compile 'commons-logging:commons-logging:1.2'
        testCompile 'org.springframework:spring-test:4.1.4.RELEASE'
        testCompile 'org.testng:testng:6.1.1'
    }

    test {
        // enable TestNG support (default is JUnit)
        useTestNG() 
    }
}

// Resolve the dependencies between the layers in the individual project's build.gradle files
// add ONLY specific per project behaviour of the GLOBAL build here:

project(':contentplatform-web') {
}

project(':contentplatform-service') {
}

project(':contentplatform-dao') {
}

// Return a list of all the external libraries
def getLibraries() {
    return configurations.runtime.filter{!it.name.startsWith('contentplatform')}
}

// Copy all the libraries to a libs folder
task copyLibraries(type: Copy) {
    group 'Content Platform'
    description 'Copy all the external libraries to the /libs folder.'

    destinationDir file('./build/')

    into('libs/') {
        from getLibraries()
    }
}

// Perform the build task before building the big jar
jar {
    group 'Content Platform'
    description 'Package all the layers and dependencies into a big jar.'

    // The libraries are required to build
    dependsOn(copyLibraries)

    // The final big jar needs all the layers
    dependencies {
        compile project(':contentplatform-web'), project(':contentplatform-dao'),
            project(':contentplatform-service'), project(':contentplatform-model')
    }
    // Create a MANIFEST.MF file, the main class file is in the web layer
    manifest {
        attributes 'Implementation-Title': 'Content Platform',  
            'Implementation-Version': version,
            'Built-By': System.getProperty('user.name'),
            'Built-Date': new Date(),
            'Built-JDK': System.getProperty('java.version'),
            'Class-Path': getLibraries().collect{'../libs/' + it.getName()}.join(' '),
            'Main-Class': mainClassName
    }

    // Include the layers in the fat jar
    from(configurations.compile.filter{it.name.startsWith('contentplatform')}.collect{it.isDirectory() ? it : zipTree(it) }) {
        exclude "META-INF/*.SF"
        exclude "META-INF/*.DSA"
        exclude "META-INF/*.RSA"
    }

    // Save the fat jar in the root of the folder instead of in build/libs
    destinationDir file('.')
}

What logging framework is used ? I would provide custom config file to it instead of setting it via API. I think java.util.logging is used, my choice would be jul--over-slf4j + slf4j-api + logback-classic, then set loggers and appenders in logback's config file.

If I understand correctly you have to generate Report from all executed TestNG cases.

However, from code which you shared, it is very visible that you will have some trouble with it. You are making a few critical mistakes and result are obvious:

• For generating reports with TestNG I will suggest grabbing information about test execution from TestNG listener. Something like:

  public final class TestNGListener extends TestListenerAdapter implements IInvokedMethodListener, ISuiteListener {
  
  @Override
  public void onStart(ITestContext context) {
      Logger.info(buildMessage(Logger.PREFIX_TEST_STARTED, context.getName()));
  }
  
  @Override
  public void onFinish(ITestContext context) {
      Logger.info(buildMessage(Logger.PREFIX_TEST_FINISHED, context.getName()));
  }
  
  @Override
  public void onTestStart(ITestResult result) {
      Logger.info(buildMessage(Logger.PREFIX_METHOD_STARTED, getMethodName(result)));
  }
  
  @Override
  public void onTestSuccess(ITestResult result) {
      Logger.info(buildMessage(Logger.PREFIX_METHOD_SUCCESS, getMethodName(result)));
      processTestResult(result);
  }
  
  @Override
  public void onTestFailure(ITestResult result) {
      Logger.info(buildMessage(Logger.PREFIX_METHOD_FAILED, getMethodName(result)));
  }
  

• You can't do everything in one method! You broke Single Responsibility Principle. Your createInstanceReport() is doing all jobs (setting report details, set system info, attach an executed test case to report) at one place. You have to redesign this logic to some logical separate operations. After redesigning your problem with the next line:

Reporting.extentReports.set(extentReports)

Could successfully disappear.

• You have to consider a case, why you need to use exactly Extent, Reports Version 3. TestNG has test reports from the box. They are poor but they are presented out of the box. If you want just to improve it a little bit you could use ReportNG over TestNG.

It is quite easy to configure: Configuring ReportNG with TestNG for HTML Reports.

It isn't maintained, but it makes TestNG reports really eye candy and understandable.

Anyway, my suggestion is to use TestNGListener for getting info about test cases execution. And read more about good programming practice.

Created testng suite file manually as below:

1. Run once your project from Eclipse
2. Refresh your project
3. Now, “test-output” folder will be created under your project –> unfold the folder
4. Double click the ‘index.html’ file -> It will be opened in the Eclipse Browser window or any other external browser (e.g. IE, Google Chrome, FF, MS Edge etc.)
5. Click on the ‘.xml’ link given on the left panel
6. The test suite XML will get opened on the right-side panel
7. Take a copy of the XML content
8. Right click your project >> New >> File
9. Give name of your test suite file (with .xml extension e.g. testng.xml) and click Finish
10. Paste the content that you copied from the ‘index.html’ and amend your suite file as per your needs

Your code is missing the annotation

@PrepareForTest(IdGenerator.class)