Skip to content

Commit 311bc39

Browse files
authored
Fix docs about CachingMode (#955)
1 parent db9b750 commit 311bc39

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/core-concepts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -148,11 +148,11 @@ beforeEachTest {
148148
You can pass in an optional parameter to `memoized` which controls how the values are cached.
149149

150150
- `CachingMode.TEST`: each test scope will receive a unique instance, this is the default.
151-
- `CachingMode.GROUP`: each group scope will receive a unique instance.
151+
- `CachingMode.EACH_GROUP`: each group scope will receive a unique instance.
152152
- `CachingMode.SCOPE`: effectively a singleton.
153153
- `CachingMode.INHERIT`: internal use only.
154154

155-
If you are using the [gherkin](gherkin.md) style note that the default caching mode is `CachingMode.GROUP`.
155+
If you are using the [gherkin](gherkin.md) style note that the default caching mode is `CachingMode.EACH_GROUP`.
156156

157157
### Share common logic between tests
158158
Often there is some code, which needs to be called repeatedly before and after tests.

docs/gherkin.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Describes a business rule, it consists of a list of steps.
6363
- `And`: Can be used as an alternative to additional `Given`, `When`, or `Then` steps.
6464

6565
## Scope values
66-
The default caching mode for `memoized` is `CachingMode.GROUP`, which means that every scenario will have a unique instance.
66+
The default caching mode for `memoized` is `CachingMode.EACH_GROUP`, which means that every scenario will have a unique instance.
6767

6868
## Best practices
6969
### Validating a side-effect

0 commit comments

Comments
 (0)