TNG/junit-dataprovider issues and pull requests

#95 - Can we used cucumber with junit-dataprovider?

Issue - State: closed - Opened by gaponte1985 over 7 years ago - 8 comments
Labels: type: question, component: junit4, status: waiting external

#94 - Support running as a JUnit Rule instead of a JUnit Runner

Issue - State: closed - Opened by dalewking over 7 years ago - 8 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#94 - Support running as a JUnit Rule instead of a JUnit Runner

Issue - State: closed - Opened by dalewking over 7 years ago - 8 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#94 - Support running as a JUnit Rule instead of a JUnit Runner

Issue - State: closed - Opened by dalewking over 7 years ago - 8 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#93 - Should I expect the dataprovider to run 3x if there are 3 tests?

Issue - State: closed - Opened by BrianJavaJazz over 7 years ago - 7 comments
Labels: type: enhancement, resolution: fixed

#92 - Can Gradle run these tests in parallel?

Issue - State: closed - Opened by thejohnfreeman over 7 years ago - 12 comments
Labels: type: question, status: discussion, component: external

#92 - Can Gradle run these tests in parallel?

Issue - State: closed - Opened by thejohnfreeman over 7 years ago - 12 comments
Labels: type: question, status: discussion, component: external

#91 - README.md: fix release notes link

Pull Request - State: closed - Opened by PascalSchumacher over 7 years ago - 2 comments

#90 - Show test parameter names in test name?

Issue - State: closed - Opened by PascalSchumacher over 7 years ago - 12 comments
Labels: type: enhancement, resolution: fixed, component: core

#90 - Show test parameter names in test name?

Issue - State: closed - Opened by PascalSchumacher over 7 years ago - 12 comments
Labels: type: enhancement, resolution: fixed, component: core

#90 - Show test parameter names in test name?

Issue - State: closed - Opened by PascalSchumacher over 7 years ago - 12 comments
Labels: type: enhancement, resolution: fixed, component: core

#89 - support Named parameters

Issue - State: closed - Opened by ChristianSchwarz over 7 years ago - 11 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#89 - support Named parameters

Issue - State: closed - Opened by ChristianSchwarz over 7 years ago - 11 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#88 - Automatically create subtree when dataprovider is used

Issue - State: closed - Opened by nikowitt over 7 years ago - 6 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#88 - Automatically create subtree when dataprovider is used

Issue - State: closed - Opened by nikowitt over 7 years ago - 6 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#88 - Automatically create subtree when dataprovider is used

Issue - State: closed - Opened by nikowitt over 7 years ago - 6 comments
Labels: type: enhancement, resolution: wontfix, component: junit4

#87 - Overridden @Test with @UseDataProvider is executed twice

Issue - State: closed - Opened by nikowitt over 7 years ago - 8 comments
Labels: type: defect, resolution: wontfix, component: junit4

#87 - Overridden @Test with @UseDataProvider is executed twice

Issue - State: closed - Opened by nikowitt over 7 years ago - 8 comments
Labels: type: defect, resolution: wontfix, component: junit4

#86 - Support of wildcards in DataConverter.canConvert

Issue - State: closed - Opened by nikowitt over 7 years ago - 4 comments
Labels: type: defect

#86 - Support of wildcards in DataConverter.canConvert

Issue - State: closed - Opened by nikowitt over 7 years ago - 4 comments
Labels: type: defect

#85 - Loading DataProviderMethodResolver via java.util.ServiceLoader ...

Issue - State: closed - Opened by aaschmid almost 8 years ago - 2 comments
Labels: type: enhancement, resolution: wontfix

#85 - Loading DataProviderMethodResolver via java.util.ServiceLoader ...

Issue - State: closed - Opened by aaschmid almost 8 years ago - 2 comments
Labels: type: enhancement, resolution: wontfix

#85 - Loading DataProviderMethodResolver via java.util.ServiceLoader ...

Issue - State: closed - Opened by aaschmid almost 8 years ago - 2 comments
Labels: type: enhancement, resolution: wontfix

#84 - Loading Placeholders via java.util.ServiceLoader

Issue - State: closed - Opened by aaschmid almost 8 years ago - 1 comment
Labels: type: enhancement, resolution: wontfix

#84 - Loading Placeholders via java.util.ServiceLoader

Issue - State: closed - Opened by aaschmid almost 8 years ago - 1 comment
Labels: type: enhancement, resolution: wontfix

#84 - Loading Placeholders via java.util.ServiceLoader

Issue - State: closed - Opened by aaschmid almost 8 years ago - 1 comment
Labels: type: enhancement, resolution: wontfix

#83 - Name of the scenario for each provider iteration

Issue - State: closed - Opened by neoshadybeat almost 8 years ago - 5 comments
Labels: type: enhancement, component: junit4, status: waiting external

#83 - Name of the scenario for each provider iteration

Issue - State: closed - Opened by neoshadybeat almost 8 years ago - 5 comments
Labels: type: enhancement, component: junit4, status: waiting external

#83 - Name of the scenario for each provider iteration

Issue - State: closed - Opened by neoshadybeat almost 8 years ago - 5 comments
Labels: type: enhancement, component: junit4, status: waiting external

#82 - Add @BeforeDataProvider and @AfterDataProvider methods

Issue - State: closed - Opened by aaschmid about 8 years ago - 8 comments
Labels: type: enhancement, type: question, resolution: declined

#82 - Add @BeforeDataProvider and @AfterDataProvider methods

Issue - State: closed - Opened by aaschmid about 8 years ago - 8 comments
Labels: type: enhancement, type: question, resolution: declined

#82 - Add @BeforeDataProvider and @AfterDataProvider methods

Issue - State: closed - Opened by aaschmid about 8 years ago - 8 comments
Labels: type: enhancement, type: question, resolution: declined

#81 - @Before is support?

Issue - State: closed - Opened by shenxj1228 about 8 years ago - 3 comments
Labels: type: question

#81 - @Before is support?

Issue - State: closed - Opened by shenxj1228 about 8 years ago - 3 comments
Labels: type: question

#80 - Incorrect work with Maven test plugins

Issue - State: closed - Opened by dmaidaniuk over 8 years ago - 5 comments
Labels: type: question

#80 - Incorrect work with Maven test plugins

Issue - State: closed - Opened by dmaidaniuk over 8 years ago - 5 comments
Labels: type: question

#80 - Incorrect work with Maven test plugins

Issue - State: closed - Opened by dmaidaniuk over 8 years ago - 5 comments
Labels: type: question

#79 - Since multiple @RunWith impossible, a static way to initialize the Runner is needed

Issue - State: closed - Opened by sxilderik over 8 years ago - 21 comments
Labels: type: question

#79 - Since multiple @RunWith impossible, a static way to initialize the Runner is needed

Issue - State: closed - Opened by sxilderik over 8 years ago - 21 comments
Labels: type: question

#79 - Since multiple @RunWith impossible, a static way to initialize the Runner is needed

Issue - State: closed - Opened by sxilderik over 8 years ago - 21 comments
Labels: type: question

#78 - it would be better if it was List<? extends Object> and not just List

Issue - State: closed - Opened by aaschmid over 8 years ago - 3 comments
Labels: type: enhancement, resolution: fixed

#78 - it would be better if it was List<? extends Object> and not just List

Issue - State: closed - Opened by aaschmid over 8 years ago - 3 comments
Labels: type: enhancement, resolution: fixed

#78 - it would be better if it was List<? extends Object> and not just List

Issue - State: closed - Opened by aaschmid over 8 years ago - 3 comments
Labels: type: enhancement, resolution: fixed

#77 - Can not use list as parameter?

Issue - State: closed - Opened by PascalSchumacher over 8 years ago - 3 comments

#77 - Can not use list as parameter?

Issue - State: closed - Opened by PascalSchumacher over 8 years ago - 3 comments

#77 - Can not use list as parameter?

Issue - State: closed - Opened by PascalSchumacher over 8 years ago - 3 comments

#76 - Allow additional convention for @DataProvider method name

Issue - State: closed - Opened by PascalSchumacher over 8 years ago - 4 comments
Labels: type: enhancement, resolution: fixed

#76 - Allow additional convention for @DataProvider method name

Issue - State: closed - Opened by PascalSchumacher over 8 years ago - 4 comments
Labels: type: enhancement, resolution: fixed

#76 - Allow additional convention for @DataProvider method name

Issue - State: closed - Opened by PascalSchumacher over 8 years ago - 4 comments
Labels: type: enhancement, resolution: fixed

#75 - Support for JUnit 5

Issue - State: closed - Opened by aburmeis over 8 years ago - 23 comments
Labels: type: enhancement, resolution: fixed, component: junit-jupiter, component: junit-jupiter-params

#75 - Support for JUnit 5

Issue - State: closed - Opened by aburmeis over 8 years ago - 23 comments
Labels: type: enhancement, resolution: fixed, component: junit-jupiter, component: junit-jupiter-params

#75 - Support for JUnit 5

Issue - State: closed - Opened by aburmeis over 8 years ago - 23 comments
Labels: type: enhancement, resolution: fixed, component: junit-jupiter, component: junit-jupiter-params

#74 - NPE for null VarArgs

Pull Request - State: closed - Opened by moritzp over 8 years ago - 1 comment

#74 - NPE for null VarArgs

Pull Request - State: closed - Opened by moritzp over 8 years ago - 1 comment

#74 - NPE for null VarArgs

Pull Request - State: closed - Opened by moritzp over 8 years ago - 1 comment

#73 - Tests fail if using \0 character in test data

Issue - State: closed - Opened by aaschmid over 8 years ago

#73 - Tests fail if using \0 character in test data

Issue - State: closed - Opened by aaschmid over 8 years ago

#73 - Tests fail if using \0 character in test data

Issue - State: closed - Opened by aaschmid over 8 years ago

#72 - Assertj update

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 6 comments

#72 - Assertj update

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 6 comments

#72 - Assertj update

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 6 comments

#71 - update maven build:

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 1 comment

#71 - update maven build:

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 1 comment

#71 - update maven build:

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 1 comment

#70 - Ability to reference multiple data providers

Issue - State: closed - Opened by aaschmid over 8 years ago - 3 comments
Labels: type: enhancement, type: question

#70 - Ability to reference multiple data providers

Issue - State: closed - Opened by aaschmid over 8 years ago - 3 comments
Labels: type: enhancement, type: question

#70 - Ability to reference multiple data providers

Issue - State: closed - Opened by aaschmid over 8 years ago - 3 comments
Labels: type: enhancement, type: question

#69 - added crossproduct of data providers

Pull Request - State: closed - Opened by ritschwumm over 8 years ago - 8 comments
Labels: type: enhancement

#69 - added crossproduct of data providers

Pull Request - State: closed - Opened by ritschwumm over 8 years ago - 8 comments
Labels: type: enhancement

#69 - added crossproduct of data providers

Pull Request - State: closed - Opened by ritschwumm over 8 years ago - 8 comments
Labels: type: enhancement

#68 - simplified some assertions by using #containsExactly

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 5 comments
Labels: type: refactoring

#68 - simplified some assertions by using #containsExactly

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 5 comments
Labels: type: refactoring

#68 - simplified some assertions by using #containsExactly

Pull Request - State: closed - Opened by PascalSchumacher over 8 years ago - 5 comments
Labels: type: refactoring

#67 - Support List<Object> for 1 parameter tests

Issue - State: closed - Opened by drdamour over 8 years ago - 4 comments
Labels: type: enhancement

#67 - Support List<Object> for 1 parameter tests

Issue - State: closed - Opened by drdamour over 8 years ago - 4 comments
Labels: type: enhancement

#67 - Support List<Object> for 1 parameter tests

Issue - State: closed - Opened by drdamour over 8 years ago - 4 comments
Labels: type: enhancement

#66 - NullPointerException when toString() of parameter returns null

Issue - State: closed - Opened by PascalSchumacher almost 9 years ago - 4 comments
Labels: type: defect, resolution: fixed

#66 - NullPointerException when toString() of parameter returns null

Issue - State: closed - Opened by PascalSchumacher almost 9 years ago - 4 comments
Labels: type: defect, resolution: fixed

#66 - NullPointerException when toString() of parameter returns null

Issue - State: closed - Opened by PascalSchumacher almost 9 years ago - 4 comments
Labels: type: defect, resolution: fixed

#65 - Running junit-dataprovider with Maven unable to generate test results

Issue - State: closed - Opened by whypurplishblue almost 9 years ago - 3 comments
Labels: type: defect

#65 - Running junit-dataprovider with Maven unable to generate test results

Issue - State: closed - Opened by whypurplishblue almost 9 years ago - 3 comments
Labels: type: defect

#65 - Running junit-dataprovider with Maven unable to generate test results

Issue - State: closed - Opened by whypurplishblue almost 9 years ago - 3 comments
Labels: type: defect

#64 - Before/AfterClass invoked at wrong time for abstract classes in suites

Issue - State: closed - Opened by seanf almost 9 years ago - 10 comments
Labels: type: defect

#64 - Before/AfterClass invoked at wrong time for abstract classes in suites

Issue - State: closed - Opened by seanf almost 9 years ago - 10 comments
Labels: type: defect

#63 - Combination of string based @DataProvider and @UseDataProvider

Issue - State: closed - Opened by nikowitt almost 9 years ago - 13 comments
Labels: type: enhancement, resolution: fixed

#63 - Combination of string based @DataProvider and @UseDataProvider

Issue - State: closed - Opened by nikowitt almost 9 years ago - 13 comments
Labels: type: enhancement, resolution: fixed

#63 - Combination of string based @DataProvider and @UseDataProvider

Issue - State: closed - Opened by nikowitt almost 9 years ago - 13 comments
Labels: type: enhancement, resolution: fixed

#62 - [Eclipse] DataProvider using custom types

Issue - State: closed - Opened by CrystalMethod almost 9 years ago - 4 comments

#62 - [Eclipse] DataProvider using custom types

Issue - State: closed - Opened by CrystalMethod almost 9 years ago - 4 comments

#62 - [Eclipse] DataProvider using custom types

Issue - State: closed - Opened by CrystalMethod almost 9 years ago - 4 comments

#61 - @DataProvider's splitBy should be only invoked when it is required

Issue - State: closed - Opened by nikowitt almost 9 years ago - 4 comments
Labels: type: enhancement

#61 - @DataProvider's splitBy should be only invoked when it is required

Issue - State: closed - Opened by nikowitt almost 9 years ago - 4 comments
Labels: type: enhancement

#61 - @DataProvider's splitBy should be only invoked when it is required

Issue - State: closed - Opened by nikowitt almost 9 years ago - 4 comments
Labels: type: enhancement

#60 - Ignoring single datapoints

Issue - State: closed - Opened by moritzp almost 9 years ago - 10 comments
Labels: type: enhancement, component: junit4

#60 - Ignoring single datapoints

Issue - State: closed - Opened by moritzp almost 9 years ago - 10 comments
Labels: type: enhancement, component: junit4

#60 - Ignoring single datapoints

Issue - State: closed - Opened by moritzp almost 9 years ago - 10 comments
Labels: type: enhancement, component: junit4

#59 - Buggy Eclipse behaviour when object's toString() implementation contains a new line and is used in @DataProvider

Issue - State: closed - Opened by nikowitt almost 9 years ago - 5 comments
Labels: type: defect

#59 - Buggy Eclipse behaviour when object's toString() implementation contains a new line and is used in @DataProvider

Issue - State: closed - Opened by nikowitt almost 9 years ago - 5 comments
Labels: type: defect

#59 - Buggy Eclipse behaviour when object's toString() implementation contains a new line and is used in @DataProvider

Issue - State: closed - Opened by nikowitt almost 9 years ago - 5 comments
Labels: type: defect

#58 - Ignore case for enum strings

Issue - State: closed - Opened by nikowitt almost 9 years ago - 9 comments
Labels: type: enhancement, resolution: fixed

GitHub / TNG/junit-dataprovider issues and pull requests