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
This issue tracks the status of Gherkin-Rust implementation in terms of the specifications and data used in the upstream project.
The purpose of this issue is to track status. Please open a new issue if you wish to record or discuss a feature and its implementation.
Each item should be checked off once the specification and data and exactly match. NA items should be checked off once there is a spec/test confirming that no output is produced.
Any partial matches should be noted but not checked off.
In order to determine a match or not we rely on the Cucumber Compatibility Kit (CCK). The CCK allows certain fields to be different from the golden master, such as: SourceReference fields used in support code messages, Duration and Timestamp fields id fields.
bbros-dev
changed the title
[Spec] Upstream alignment status: Bad specifications and data
[Spec] Upstream alignment status: Unhappy-path specifications and data
Mar 4, 2021
This issue tracks the status of Gherkin-Rust implementation in terms of the specifications and data used in the upstream project.
The purpose of this issue is to track status. Please open a new issue if you wish to record or discuss a feature and its implementation.
Each item should be checked off once the specification and data and exactly match. NA items should be checked off once there is a spec/test confirming that no output is produced.
Any partial matches should be noted but not checked off.
In order to determine a match or not we rely on the Cucumber Compatibility Kit (CCK). The CCK allows certain fields to be different from the golden master, such as:
SourceReference
fields used in support code messages,Duration
andTimestamp
fieldsid
fields.The upstream data is here:
The specifications and data in Gherkin-Rust are circa 27-Feb 2021, commit 109f9a3.
Please open a pull request if you notice any specification or data has changed.
The text was updated successfully, but these errors were encountered: