You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: system-stubs-junit4/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ project and has been rebuilt from the ground up for this version.
9
9
<dependency>
10
10
<groupId>uk.org.webcompere</groupId>
11
11
<artifactId>system-stubs-junit4</artifactId>
12
-
<version>1.2.0</version>
12
+
<version>2.0.1</version>
13
13
</dependency>
14
14
```
15
15
@@ -250,4 +250,4 @@ other situations, and need to make these work in JUnit 4 also.
250
250
251
251
There are extensive tests demonstrating each of the JUnit rules. However, in some situations, you may need finer control of the System Stub objects. You can always mix using rules and core objects via the `execute` pattern. It may also be easier to combine methods from `SystemStubs` with some common rules.
252
252
253
-
It is worth noting that putting common set up into a `@Rule` object is useful unless there is nothing common between test cases. In that instance, consider having multiple test classes for each configuration, or using only the most essential common setup within rules, and adding the `execute` pattern for variations.
253
+
It is worth noting that putting common set up into a `@Rule` object is useful unless there is nothing common between test cases. In that instance, consider having multiple test classes for each configuration, or using only the most essential common setup within rules, and adding the `execute` pattern for variations.
0 commit comments