Skip to content
TestNG testing framework
Java CSS Kotlin HTML JavaScript Shell Other
Branch: master
Clone or download

Latest commit

juherr Merge pull request #2316 from JamesSassano/master
TextReporter can log data provider arrays from object's toString()
Fix #2315
Latest commit 7ce15ca May 29, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github All the other http:// -> https:// Feb 19, 2020
bin Upgrading to JDK8 Mar 24, 2018
gradle All the other http:// -> https:// Feb 19, 2020
kobalt All the other http:// -> https:// Feb 19, 2020
src TextReporter can log data provider arrays from object's toString() (#… May 29, 2020
.gitignore Revert auto-generated file; add 'ignore' for same May 11, 2020
.mailmap Fix contributors info from commit Oct 26, 2015
.travis.yml Use Trusty environment for oracle jdk8 Aug 5, 2019
ANNOUNCEMENT.txt All the other http:// -> https:// Feb 19, 2020
CHANGES.txt TextReporter can log data provider arrays from object's toString() (#… May 29, 2020
CHECKLIST Added CHECKLIST for releases. Jul 15, 2012
CONTRIBUTING.md
LICENSE.txt All the other http:// -> https:// Feb 19, 2020
README-publish More instructions to deploy to Maven Central Jun 30, 2019
README.dev All the other http:// -> https:// Feb 19, 2020
README.md All the other http:// -> https:// Feb 19, 2020
appveyor.yml Use AppVeyor as Windows CI Jun 1, 2015
build-with-gradle Remove redundant cleanTest; use gradle daemon May 31, 2015
build.gradle.kts Fix doclint errors and warnings May 14, 2020
deploy-to-maven Automatically close and promote on Nexus. Jul 14, 2015
gradlew Upgrade to Gradle 6 Jan 5, 2020
gradlew.bat Upgrade to Gradle 6 Jan 5, 2020
kobaltw Update Kobalt. Sep 16, 2016
settings.gradle.kts Upgrade to Gradle 6 Jan 5, 2020
travis.sh Fix sonar keys and disable publishing locally Mar 11, 2020

README.md

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

Documentation available at TestNG's main web site.

Release Notes

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.

You can’t perform that action at this time.