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
Added new dependency on cucumber-query which is a new internal structure for all message based formatters to query the state
of the test run (#1889luke-hill & mattwynne)
Changed
Updated cucumber-compatibility-kit to v26
Refactor to internal error logic (No user facing changes)
Refactor to internal MessageBuilder logic (No user facing changes)
Cucumber::Runtime#ask which has not been actively supported is now deprecated (Should you wish to delay things
and wait for input, either use a tool like pry or add a hard-coded sleep) (#1842luke-hill)
Updated cucumber-expressions to v20
Updated cucumber-html-formatter to v24
Permit multi_test v2/v3 so we can begin to remove some legacy support
Updated cucumber-core to v20
All events now inherit from the new Cucumber::Core::Event::Base class (luke-hill)
Updated the MessageBuilder to not create the messages now created by cucumber-ruby-core (#1882brasmusson)
Fixed
The testCaseFinished message now states willBeRetried correctly when --retry-total stops further retries, or when --retry is used at all (it was off by one), so the HTML formatter no longer drops or duplicates scenarios
(#1905Enceradeira)
Updated the html-formatter to access message stream correctly (#1899brasmusson)
Removed
This was a long-standing feature that was used to determine if a test run should fail if there were any undefined, pending or flaky steps.
All non-passing scenarios (Except flaky with retry), are now considered failures
Removed the concept of strict from cucumber-ruby (luke-hill)
Removed a bunch of RSpec support logic that was no longer used in the codebase (This includes some legacy pending
logic and some old rspec helper files)
Removed handling of a Ruby 2.1 system error (luke-hill)
Removed support for Ruby 3.1 and 3.2 (Minimum ruby is now 3.3) (luke-hill)
Removed the duplicated "new" base class for events - use Core::Event::Base instead (luke-hill)