TestNG testing framework
Branch: master
Clone or download
krmahadevan Merge pull request #2013 from krmahadevan/fix_2003
Add to @test interface fields IDs and issues
Latest commit 1082fa6 Feb 1, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Adding user facing documentation to README Mar 5, 2017
bin Upgrading to JDK8 Mar 24, 2018
gradle Gradle 5.0 upgrade Jan 20, 2019
kobalt Support all JSR-223 compatible script engine (#1847) Jul 1, 2018
src Add to @test interface fields IDs and issues Feb 1, 2019
.gitignore
.mailmap Fix contributors info from commit Oct 26, 2015
.travis.yml Upgrading to JDK8 Mar 24, 2018
ANNOUNCEMENT.txt
CHANGES.txt Add to @test interface fields IDs and issues Feb 1, 2019
CHECKLIST Added CHECKLIST for releases. Jul 15, 2012
CONTRIBUTING.md Update CONTRIBUTING.md Oct 24, 2017
LICENSE.txt Initial commit Aug 1, 2006
README-publish README-publish Oct 27, 2015
README.dev Instructions updates. Dec 18, 2014
README.md Fix Sonarcloud badge Jan 21, 2019
appveyor.yml Use AppVeyor as Windows CI Jun 1, 2015
build-with-gradle Remove redundant cleanTest; use gradle daemon May 31, 2015
build.gradle Gradle 5.0 upgrade Jan 20, 2019
deploy-to-maven Automatically close and promote on Nexus. Jul 14, 2015
gradlew Gradle 5.0 upgrade Jan 20, 2019
gradlew.bat Gradle 5.0 upgrade Jan 20, 2019
kobaltw Update Kobalt. Sep 16, 2016
settings.gradle Gradle 5.0 upgrade Jan 20, 2019
travis.sh Fixing publishing problem Jun 8, 2018

README.md

Build Status Maven Central Bintray License Sonarqube tech debt Sonarqube Quality Gate Status

Documentation available at TestNG's main web site.

Need help?

Before opening a new issue, did you ask your question on

If you posted on both sites, please provide the link to the other question to avoid duplicating the answer.

Are you sure it is a TestNG bug?

Before posting the issue, try to reproduce the issue in a shell window.

If the problem does not exist with the shell, first check if the issue exists on the bugtracker of the runner, and open an issue there first:

Which version are you using?

Always make sure your issue is happening on the latest TestNG version. Bug reports occurring on older versions will not be looked at quickly.

Have you considered sending a pull request instead of filing an issue?

The best way to report a bug is to provide the TestNG team with a full test case reproducing the issue. Maybe you can write a runnable test case (check the src/test/ folder for examples) and propose it in a pull request Don't worry if the CI fails because it is the expected behavior. This pull request will be a perfect start to find the fix :)

How to create a pull request?

Refer our Contributing section for detailed set of steps.

We encourage pull requests that:

  • Add new features to TestNG (or)
  • Fix bugs in TestNG

If your pull request involves fixing SonarQube issues then we would suggest that you please discuss this with the TestNG-dev before you spend time working on it.