Skip to content

Commit f532bc6

Browse files
committed
update docs
1 parent ff83a04 commit f532bc6

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

README.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -250,7 +250,13 @@ Not supported:
250250

251251
Of course, constructor parameters injection is not supported because spock does not allow spec constructors.
252252

253-
##### Default extensions
253+
**What does "extension not supported" mean?**
254+
If extension implements not supported extension interface, like `TestWatcher`,
255+
then methods for this interface would not be called on extension. That's all.
256+
Such interfaces might be used in extension for some "additional features" like logging and
257+
so extension would work perfectly in spock.
258+
259+
##### Default junit extensions
254260

255261
Junit register some extensions by default:
256262

@@ -270,6 +276,11 @@ Plus, junit loads extensions from `META-INF/services/org.junit.jupiter.api.exten
270276
This is intentional: as not all extensions are supported, then automatic loading may
271277
cause unexpected behavior. If you need any default extension - register it manually.
272278

279+
Annotation-based extensions like `@Disabled` or `@AutoClose` would work in spock because they are declared with annotations.
280+
Extensions like `TestInfoParameterResolver` could be easully enabled with `@ExtendWith(TestInfoParameterResolver.class)`
281+
282+
So overall not automatic defaults should not be a problem.
283+
273284
### Usage with Spring-Boot
274285

275286
Only spock and spock-junit5 dependencies would be required:

0 commit comments

Comments
 (0)