Skip to content

Conversation

@carlos-granados
Copy link
Contributor

In this case we could not re-use the fixtures as they were very different from the existing ones

Comment on lines 14 to 28
When I run "behat features/rerun_strict.feature"
And I run "behat --rerun features/rerun_strict.feature"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the comments on #1764 - in this feature we don't have a separate scenario that proves the fixture is broken at first (which is correct IMO).

However our initial When I run "behat features/rerun_strict.feature" in both scenarios should assert the expected result & output so that we can see how it differs on the second --rerun execution.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@carlos-granados carlos-granados force-pushed the refactor-rerun-strict-tests branch from dd9cf0d to 6095bcd Compare December 9, 2025 14:21
Copy link
Contributor

@acoulton acoulton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thanks @carlos-granados

@carlos-granados carlos-granados merged commit 31a1be0 into Behat:3.x Dec 9, 2025
22 checks passed
@carlos-granados carlos-granados deleted the refactor-rerun-strict-tests branch December 9, 2025 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants