Skip to content

Update MessageBuilder when runner generate messages#1882

Draft
brasmusson wants to merge 12 commits into
mainfrom
feature/runner-messages
Draft

Update MessageBuilder when runner generate messages#1882
brasmusson wants to merge 12 commits into
mainfrom
feature/runner-messages

Conversation

@brasmusson

@brasmusson brasmusson commented May 31, 2026

Copy link
Copy Markdown
Contributor

Description

  • Changes when the runner generate messages at the source.

Depend on cucumber/cucumber-ruby-core#331

Type of change

Please delete options that are not relevant.

  • Refactoring (improvements to code design or tooling that don't change behaviour)
  • New feature (non-breaking change which adds new behaviour)

Please add an entry to the relevant section of CHANGELOG.md as part of this pull request.

Checklist:

Your PR is ready for review once the following checklist is
complete. You can also add some checks if you want to.

  • Tests have been added for any changes to behaviour of the code
  • New and existing tests are passing locally and on CI
  • bundle exec rubocop reports no offenses
  • RDoc comments have been updated
  • CHANGELOG.md has been updated

luke-hill and others added 12 commits May 26, 2026 15:32
* Add envelope generation at source for gherkin_source_read event

* Do not double fire events
…kFinished (#1878)

* Add in logic for both run hook events to be passed as messages

* Store test_run_started_id cache on config class instance

* Pass in the test_run_started_id on hook_run_started message generation and remove faux update from envelope emittence
…_source' into feature/v11_message_emittence_at_source
* Until the attchment messages are generated at the source, the
  MessageBuilder need to keep track of the id of the current
  test run hook to be able to generate the attachment messages
  correctly.
* Changes when the runner generate test_case_started/finished messages
  at the source.
Base automatically changed from feature/v11_message_emittence_at_source to main June 1, 2026 19:51
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