Skip to content

Commit

Permalink
better wording (thanks @janschaefer)
Browse files Browse the repository at this point in the history
  • Loading branch information
aaschmid committed May 12, 2014
1 parent 41087c3 commit 893ad6f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ Motivation and distinction
> all test methodes to run, before validating and filtering it. At this points of execution, though, no instance of the
> test class is instanciated.
> Then as a second step [JUnit][] creates a single instance of the class under test for every single test method.
> One possiblity, for sure, junit-dataprovider could create an instance and invoke the ```@DataProvider```
> One possiblity, for sure, is that junit-dataprovider could create an instance and invoke the ```@DataProvider```
> as [junitparams][] does interally, but neither ```@Before``` nor ```MethodeRule``` is minded.
> Therefore, I decided to disallow a ```@DataProvider``` instance methods that nobody using junit-dataprovider
> believes accessing data of a test class instance is possible.
Expand Down

0 comments on commit 893ad6f

Please sign in to comment.