TNG/junit-dataprovider issues and pull requests

#138 - rerunFailingTestsCount + @DataProvider = failed tests are recognized as flakes

Issue - State: open - Opened by camproto almost 2 years ago - 9 comments
Labels: component: junit4

#137 - Fix NoClassDefFoundError with JUnit 5.9

Pull Request - State: closed - Opened by jenschude almost 2 years ago - 4 comments

#136 - NoClassDefFoundError with junit jupiter 5.9

Issue - State: closed - Opened by jenschude almost 2 years ago - 8 comments
Labels: type: enhancement, component: junit-jupiter, component: junit-jupiter-params, status: in progress

#136 - NoClassDefFoundError with junit jupiter 5.9

Issue - State: closed - Opened by jenschude almost 2 years ago - 8 comments
Labels: type: enhancement, component: junit-jupiter, component: junit-jupiter-params, status: in progress

#135 - Allow running of individual test methods via Gradle in conjunction with junit-vintage-runner

Pull Request - State: closed - Opened by tngwoerleij over 2 years ago - 1 comment

#135 - Allow running of individual test methods via Gradle in conjunction with junit-vintage-runner

Pull Request - State: closed - Opened by tngwoerleij over 2 years ago - 1 comment

#134 - FrameworkMethod didn't get the right test

Issue - State: closed - Opened by laaron2008 almost 3 years ago - 12 comments

#133 - How to use junit-dataprovider with powermock

Issue - State: closed - Opened by zzkyeee over 3 years ago - 3 comments
Labels: type: question

#133 - How to use junit-dataprovider with powermock

Issue - State: closed - Opened by zzkyeee over 3 years ago - 3 comments
Labels: type: question

#132 - Support lists of non-iterable parameterized type

Issue - State: closed - Opened by aaschmid over 3 years ago - 1 comment
Labels: type: defect, component: junit4

#131 - JUnit 4.13

Pull Request - State: closed - Opened by sullis about 4 years ago - 4 comments

#131 - JUnit 4.13

Pull Request - State: closed - Opened by sullis about 4 years ago - 4 comments

#130 - Use in-memory keys for signing.

Pull Request - State: closed - Opened by NilsOliverLinden about 4 years ago - 1 comment

#130 - Use in-memory keys for signing.

Pull Request - State: closed - Opened by NilsOliverLinden about 4 years ago - 1 comment

#130 - Use in-memory keys for signing.

Pull Request - State: closed - Opened by NilsOliverLinden about 4 years ago - 1 comment

#129 - Configure Renovate

Pull Request - State: closed - Opened by renovate[bot] about 4 years ago - 3 comments

#129 - Configure Renovate

Pull Request - State: closed - Opened by renovate[bot] about 4 years ago - 3 comments

#129 - Configure Renovate

Pull Request - State: closed - Opened by renovate[bot] about 4 years ago - 3 comments

#128 - Gradle wrapper validation

Pull Request - State: closed - Opened by sullis about 4 years ago - 3 comments

#128 - Gradle wrapper validation

Pull Request - State: closed - Opened by sullis about 4 years ago - 3 comments

#128 - Gradle wrapper validation

Pull Request - State: closed - Opened by sullis about 4 years ago - 3 comments

#127 - Wiki pom.xml dependency shows older version

Issue - State: closed - Opened by jaypatel512 over 4 years ago - 3 comments
Labels: resolution: fixed, component: junit4

#127 - Wiki pom.xml dependency shows older version

Issue - State: closed - Opened by jaypatel512 over 4 years ago - 3 comments
Labels: resolution: fixed, component: junit4

#126 - Maven command line doesn't recognize the automation scripts

Issue - State: closed - Opened by Harikahema1 over 4 years ago - 8 comments
Labels: type: question, status: waiting external

#126 - Maven command line doesn't recognize the automation scripts

Issue - State: closed - Opened by Harikahema1 over 4 years ago - 8 comments
Labels: type: question, status: waiting external

#125 - Fix coveralls report

Issue - State: closed - Opened by aaschmid almost 5 years ago - 2 comments
Labels: resolution: fixed, component: junit-jupiter, component: junit-jupiter-params

#125 - Fix coveralls report

Issue - State: closed - Opened by aaschmid almost 5 years ago - 2 comments
Labels: resolution: fixed, component: junit-jupiter, component: junit-jupiter-params

#124 - GitHub Actions checkout v2

Pull Request - State: closed - Opened by sullis almost 5 years ago - 1 comment
Labels: type: enhancement

#124 - GitHub Actions checkout v2

Pull Request - State: closed - Opened by sullis almost 5 years ago - 1 comment
Labels: type: enhancement

#123 - Migrate build scripts to new Kotlin DSL

Issue - State: closed - Opened by aaschmid almost 5 years ago - 1 comment
Labels: resolution: fixed, type: refactoring, component: core, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#123 - Migrate build scripts to new Kotlin DSL

Issue - State: closed - Opened by aaschmid almost 5 years ago - 1 comment
Labels: resolution: fixed, type: refactoring, component: core, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#122 - Fix and cleanup duplicates, spotbugs and fail build on new ones?

Issue - State: closed - Opened by aaschmid almost 5 years ago - 1 comment
Labels: resolution: fixed, type: refactoring, component: core, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#122 - Fix and cleanup duplicates, spotbugs and fail build on new ones?

Issue - State: closed - Opened by aaschmid almost 5 years ago - 1 comment
Labels: resolution: fixed, type: refactoring, component: core, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#121 - When will it support non static dataprovider ?

Issue - State: closed - Opened by wolfwestern about 5 years ago - 2 comments
Labels: type: question, resolution: wontfix

#120 - Unable to use DataproviderRunner with PowerMock

Issue - State: closed - Opened by Vengat about 5 years ago - 7 comments
Labels: status: discussion

#120 - Unable to use DataproviderRunner with PowerMock

Issue - State: closed - Opened by Vengat about 5 years ago - 7 comments
Labels: status: discussion

#120 - Unable to use DataproviderRunner with PowerMock

Issue - State: closed - Opened by Vengat about 5 years ago - 7 comments
Labels: status: discussion

#119 - Upgrade to maven-publish plugin as Gradle broke signing with 5.1.1

Issue - State: closed - Opened by aaschmid about 5 years ago - 2 comments
Labels: type: enhancement, resolution: fixed, type: refactoring, component: core, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#119 - Upgrade to maven-publish plugin as Gradle broke signing with 5.1.1

Issue - State: closed - Opened by aaschmid about 5 years ago - 2 comments
Labels: type: enhancement, resolution: fixed, type: refactoring, component: core, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#119 - Upgrade to maven-publish plugin as Gradle broke signing with 5.1.1

Issue - State: closed - Opened by aaschmid about 5 years ago - 2 comments
Labels: type: enhancement, resolution: fixed, type: refactoring, component: core, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#118 - Compatibilty with junit-jupiter-engine 5.4.0 or higher

Issue - State: closed - Opened by geoffreyharding about 5 years ago - 5 comments
Labels: type: defect, component: junit-jupiter, status: in progress

#118 - Compatibilty with junit-jupiter-engine 5.4.0 or higher

Issue - State: closed - Opened by geoffreyharding about 5 years ago - 5 comments
Labels: type: defect, component: junit-jupiter, status: in progress

#118 - Compatibilty with junit-jupiter-engine 5.4.0 or higher

Issue - State: closed - Opened by geoffreyharding about 5 years ago - 5 comments
Labels: type: defect, component: junit-jupiter, status: in progress

#117 - SpringRunner Docs aren't very helpful

Issue - State: closed - Opened by drdamour over 5 years ago - 10 comments

#117 - SpringRunner Docs aren't very helpful

Issue - State: closed - Opened by drdamour over 5 years ago - 10 comments

#117 - SpringRunner Docs aren't very helpful

Issue - State: closed - Opened by drdamour over 5 years ago - 10 comments

#116 - Memory leak through DataProvider?

Issue - State: closed - Opened by codecholeric over 5 years ago - 4 comments
Labels: type: enhancement, component: junit4

#116 - Memory leak through DataProvider?

Issue - State: closed - Opened by codecholeric over 5 years ago - 4 comments
Labels: type: enhancement, component: junit4

#115 - version 2.* not available in mvnrepository

Issue - State: closed - Opened by yoosiba over 5 years ago - 2 comments
Labels: type: question, resolution: wontfix

#115 - version 2.* not available in mvnrepository

Issue - State: closed - Opened by yoosiba over 5 years ago - 2 comments
Labels: type: question, resolution: wontfix

#114 - @DataProvider runs before @BeforeClass

Issue - State: closed - Opened by flocsy almost 6 years ago - 6 comments
Labels: type: defect, resolution: wontfix, component: junit4

#114 - @DataProvider runs before @BeforeClass

Issue - State: closed - Opened by flocsy almost 6 years ago - 6 comments
Labels: type: defect, resolution: wontfix, component: junit4

#113 - DataProviderRunner.class do not use rerunFailingTestsCount in parallel

Issue - State: closed - Opened by emaks about 6 years ago - 8 comments
Labels: type: defect, component: junit4, status: in progress

#113 - DataProviderRunner.class do not use rerunFailingTestsCount in parallel

Issue - State: closed - Opened by emaks about 6 years ago - 8 comments
Labels: type: defect, component: junit4, status: in progress

#113 - DataProviderRunner.class do not use rerunFailingTestsCount in parallel

Issue - State: closed - Opened by emaks about 6 years ago - 8 comments
Labels: type: defect, component: junit4, status: in progress

#112 - various dependencies updates

Pull Request - State: closed - Opened by based2 about 6 years ago - 4 comments

#112 - various dependencies updates

Pull Request - State: closed - Opened by based2 about 6 years ago - 4 comments

#112 - various dependencies updates

Pull Request - State: closed - Opened by based2 about 6 years ago - 4 comments

#111 - Unable to run specific test using mvn commandline

Issue - State: closed - Opened by praveenc79 over 6 years ago - 6 comments
Labels: type: question, resolution: fixed, component: junit4

#110 - Does it include testng @Factory annotation functionality?

Issue - State: closed - Opened by rohitgargfzr over 6 years ago - 3 comments
Labels: type: question, status: discussion, status: waiting external

#110 - Does it include testng @Factory annotation functionality?

Issue - State: closed - Opened by rohitgargfzr over 6 years ago - 3 comments
Labels: type: question, status: discussion, status: waiting external

#109 - Improve documentation of integration with Spring

Issue - State: closed - Opened by Airblader over 6 years ago - 2 comments
Labels: type: enhancement, resolution: fixed, component: junit4, status: waiting external

#109 - Improve documentation of integration with Spring

Issue - State: closed - Opened by Airblader over 6 years ago - 2 comments
Labels: type: enhancement, resolution: fixed, component: junit4, status: waiting external

#108 - Fixed self reference to contributor's agreement.

Pull Request - State: closed - Opened by codecholeric over 6 years ago - 2 comments

#108 - Fixed self reference to contributor's agreement.

Pull Request - State: closed - Opened by codecholeric over 6 years ago - 2 comments

#108 - Fixed self reference to contributor's agreement.

Pull Request - State: closed - Opened by codecholeric over 6 years ago - 2 comments

#107 - Use shields.io service for Maven badge

Pull Request - State: closed - Opened by valfirst over 6 years ago - 1 comment

#107 - Use shields.io service for Maven badge

Pull Request - State: closed - Opened by valfirst over 6 years ago - 1 comment

#107 - Use shields.io service for Maven badge

Pull Request - State: closed - Opened by valfirst over 6 years ago - 1 comment

#106 - Duplicate execution when test implements an interface

Issue - State: closed - Opened by x3rAx over 6 years ago - 5 comments
Labels: type: defect, resolution: fixed, component: junit4

#106 - Duplicate execution when test implements an interface

Issue - State: closed - Opened by x3rAx over 6 years ago - 5 comments
Labels: type: defect, resolution: fixed, component: junit4

#106 - Duplicate execution when test implements an interface

Issue - State: closed - Opened by x3rAx over 6 years ago - 5 comments
Labels: type: defect, resolution: fixed, component: junit4

#105 - Dataprovider caches results even for dynamically created data / results (e.g. using test method as parameter)

Issue - State: closed - Opened by weiro-9-w7 over 6 years ago - 14 comments
Labels: type: enhancement, resolution: fixed, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#105 - Dataprovider caches results even for dynamically created data / results (e.g. using test method as parameter)

Issue - State: closed - Opened by weiro-9-w7 over 6 years ago - 14 comments
Labels: type: enhancement, resolution: fixed, component: junit4, component: junit-jupiter, component: junit-jupiter-params

#104 - Tests are not working if test case is in base classes and dataprovider in child (executed test class) (was: Regression v.1.11.0 -> 1.12.0 ?)

Issue - State: closed - Opened by codecholeric over 6 years ago - 5 comments
Labels: type: defect, resolution: fixed, component: core, component: junit-jupiter, component: junit-jupiter-params

#104 - Tests are not working if test case is in base classes and dataprovider in child (executed test class) (was: Regression v.1.11.0 -> 1.12.0 ?)

Issue - State: closed - Opened by codecholeric over 6 years ago - 5 comments
Labels: type: defect, resolution: fixed, component: core, component: junit-jupiter, component: junit-jupiter-params

GitHub / TNG/junit-dataprovider issues and pull requests