-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
docs: call out change of after hook result in migration guide #1692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,6 +13,52 @@ You'll need to update any `import`/`require` statements in your support code to | |
|
||
(The executable is still `cucumber-js` though.) | ||
|
||
## Hooks | ||
|
||
The result object passed as the argument to your `After` hook function has a different structure. | ||
|
||
Previous in `cucumber`: | ||
|
||
```js | ||
{ | ||
"sourceLocation": { | ||
"uri": "features/example.feature", | ||
"line": 7 | ||
}, | ||
"pickle": {...}, | ||
"result": { | ||
"duration": 660000000, | ||
"status": "failed", | ||
"exception": { | ||
"name": "AssertionError", | ||
"message": "...", | ||
"showDiff": false, | ||
"stack": "..." | ||
}, | ||
"retried": true | ||
} | ||
} | ||
``` | ||
|
||
Now in `@cucumber/cucumber`: | ||
|
||
```js | ||
{ | ||
"gherkinDocument": {...}, // schema: https://github.com/cucumber/common/blob/main/messages/jsonschema/GherkinDocument.json | ||
"pickle": {...}, // schema: https://github.com/cucumber/common/blob/main/messages/jsonschema/Pickle.json | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As a note, linking to a branch has the potential of going stale. May be better to update these to a tag |
||
"testCaseStartedId": "[uuid]", | ||
"result": { | ||
"status": "FAILED", // one of: UNKNOWN, PASSED, SKIPPED, PENDING, UNDEFINED, AMBIGUOUS, FAILED | ||
"message": "...", // includes stack trace | ||
"duration": { | ||
"seconds": "0", | ||
"nanos": 660000000 | ||
}, | ||
"willBeRetried": true | ||
} | ||
} | ||
``` | ||
|
||
## Formatters | ||
|
||
The underlying event/data model for cucumber-js is now [cucumber-messages](https://github.com/cucumber/cucumber/tree/master/messages), a shared standard across all official Cucumber implementations. This replaces the old "event protocol". | ||
|
@@ -49,4 +95,4 @@ There are a few minor differences to be aware of: | |
- The type for data tables was named `TableDefinition` - it's now named `DataTable` | ||
- `World` was typed as an interface, but it's actually a class - you should `extend` it when [building a custom formatter](./custom_formatters.md) | ||
|
||
Also, your `tsconfig.json` should have the `resolveJsonModule` compiler option switched on. Other than that, a pretty standard TypeScript setup should work as expected. | ||
Also, your `tsconfig.json` should have the `resolveJsonModule` compiler option switched on. Other than that, a pretty standard TypeScript setup should work as expected. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.