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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -366,7 +366,7 @@ but all other junit extensions will work (essentially, it "applies" `@IngoreJuni
366
366
There would be a new message in log, indicating that you're using pure spock spring support (and an alternative is possible):
367
367
368
368
```
369
-
[spock-junit5] Disabling spring junit extension (org.springframework.test.context.junit.jupiter.SpringExtension) because spock-spring detected and so it will handle spring context initialization (all other junit extensions will work). If you want to run spring as junit extension, use spock-core only (without spock-spring).
369
+
[spock-junit5] Spring junit extension disabled (org.springframework.test.context.junit.jupiter.SpringExtension) because spock-spring detected and so it will handle spring context initialization (all other junit extensions will work). If you want to run spring as junit extension, use spock-core only (without spock-spring).
370
370
```
371
371
372
372
The main benefit is that you **could use** spock mocking (`@SpringBean`) and other spock features.
0 commit comments