@g_package/jest-cucumber-fusion 3.0.3 → 3.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/dist/index.d.cts +7 -3
- package/package.json +1 -1
- package/src/index.d.ts +7 -3
package/README.md
CHANGED
|
@@ -568,3 +568,5 @@ Working on the package:
|
|
|
568
568
|
* [Architecture](./docs/Architecture.md)
|
|
569
569
|
|
|
570
570
|
Every example on the guide pages above runs as written: the repository's tests copy each one into a fresh project and run it.
|
|
571
|
+
|
|
572
|
+
The [documentation index](./docs/README.md) lists all of these pages, and says what the delivery records under `docs/feature/` are.
|
package/dist/index.d.cts
CHANGED
|
@@ -102,8 +102,11 @@ export interface FusionOptions {
|
|
|
102
102
|
* An expression that cannot be parsed is refused at collection, before anything is
|
|
103
103
|
* registered, and the refusal names the expression you wrote. So is one with an operand
|
|
104
104
|
* that is not a tag, such as `smoke` written for `@smoke`: it could never match.
|
|
105
|
+
*
|
|
106
|
+
* `null` means no filter. Unlike `undefined`, which counts as not set, it is a value, so
|
|
107
|
+
* `{ tagFilter: null }` on one call clears a filter set by `setFusionConfiguration`.
|
|
105
108
|
*/
|
|
106
|
-
tagFilter?: string;
|
|
109
|
+
tagFilter?: string | null;
|
|
107
110
|
/**
|
|
108
111
|
* Renames every test Fusion registers, Scenario Outline rows included. It is called once per
|
|
109
112
|
* test while Fusion registers, never again while the tests run, and it names a test whatever
|
|
@@ -136,8 +139,9 @@ export function Fusion(feature: string, options?: FusionOptions): void;
|
|
|
136
139
|
* as `{ tagFilter: process.env.TAGS }`, counts as not set and leaves the layer below in place.
|
|
137
140
|
*
|
|
138
141
|
* A second call REPLACES what the first set rather than merging into it, which is what lets a
|
|
139
|
-
* global be cleared or redefined. Jest gives each test file its own
|
|
140
|
-
* `setupFiles` inside it
|
|
142
|
+
* global be cleared or redefined. Jest gives each test file its own global object and runs
|
|
143
|
+
* `setupFiles` inside it. The configuration lives on that global, not in a module, so what is
|
|
144
|
+
* set here cannot reach another file, and `jest.resetModules()` does not clear it.
|
|
141
145
|
*
|
|
142
146
|
* An argument that is not an options object is refused where it is called, before any step
|
|
143
147
|
* definition file has loaded. An unknown key is accepted and ignored, exactly as it is per call.
|
package/package.json
CHANGED
package/src/index.d.ts
CHANGED
|
@@ -102,8 +102,11 @@ export interface FusionOptions {
|
|
|
102
102
|
* An expression that cannot be parsed is refused at collection, before anything is
|
|
103
103
|
* registered, and the refusal names the expression you wrote. So is one with an operand
|
|
104
104
|
* that is not a tag, such as `smoke` written for `@smoke`: it could never match.
|
|
105
|
+
*
|
|
106
|
+
* `null` means no filter. Unlike `undefined`, which counts as not set, it is a value, so
|
|
107
|
+
* `{ tagFilter: null }` on one call clears a filter set by `setFusionConfiguration`.
|
|
105
108
|
*/
|
|
106
|
-
tagFilter?: string;
|
|
109
|
+
tagFilter?: string | null;
|
|
107
110
|
/**
|
|
108
111
|
* Renames every test Fusion registers, Scenario Outline rows included. It is called once per
|
|
109
112
|
* test while Fusion registers, never again while the tests run, and it names a test whatever
|
|
@@ -136,8 +139,9 @@ export function Fusion(feature: string, options?: FusionOptions): void;
|
|
|
136
139
|
* as `{ tagFilter: process.env.TAGS }`, counts as not set and leaves the layer below in place.
|
|
137
140
|
*
|
|
138
141
|
* A second call REPLACES what the first set rather than merging into it, which is what lets a
|
|
139
|
-
* global be cleared or redefined. Jest gives each test file its own
|
|
140
|
-
* `setupFiles` inside it
|
|
142
|
+
* global be cleared or redefined. Jest gives each test file its own global object and runs
|
|
143
|
+
* `setupFiles` inside it. The configuration lives on that global, not in a module, so what is
|
|
144
|
+
* set here cannot reach another file, and `jest.resetModules()` does not clear it.
|
|
141
145
|
*
|
|
142
146
|
* An argument that is not an options object is refused where it is called, before any step
|
|
143
147
|
* definition file has loaded. An unknown key is accepted and ignored, exactly as it is per call.
|