Skip to content
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

Handle internal error checks/failure assertions differently #759

Open
plocket opened this issue Sep 20, 2023 · 0 comments
Open

Handle internal error checks/failure assertions differently #759

plocket opened this issue Sep 20, 2023 · 0 comments
Labels
testing Tests for this framework

Comments

@plocket
Copy link
Collaborator

plocket commented Sep 20, 2023

To test that our users' tests fail correctly (and thus pass our tests on the Scenario level while failing on the Step level), we're modifying properties of scenario in After(). In the slack channel, cucumber is discussing making that object immutable or something like that. This comment starts that discussion.

We need a different way to pass our correctly failing tests. Another repo integrating nightwatch has been dealing with this too. I've been pointed at this file.

These are actually cucumber tests that nest their lib's tests in a sub process. So they're testing their cucumber tests with another, outer, set of cucumber tests. The outer tests make sure the correct failures happen. We can try to use the same method, though I haven't read deeply enough to truly understand how to set it up.

@plocket plocket added the testing Tests for this framework label Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Tests for this framework
Projects
None yet
Development

No branches or pull requests

1 participant