[aguspe]

Generated RSpec projects now report through raider_reporter (version 3.3.0).

Tracks RaiderHQ/raider_saas#25

Decisions

• D1 Allure stays. raider_reporter is added for RSpec projects only; Cucumber templates are unchanged.
• D2 Screenshots are taken only when example.exception is set, and each is attached to both Allure and Raider (RaiderReporter.attach('screenshot', path, type: :png)).
• D3 The generated Gemfile pins gem 'ruby_raider', '~> <MAJOR.MINOR of lib/version>' (previously a stale ~> 1.1.0).
• D4 Generated GitHub CI triggers on push (main, master), pull_request and workflow_dispatch. RSpec test steps get RAIDER_TOKEN / RAIDER_ENDPOINT, and actions/upload-artifact@v4 uploads raider-results/ with if: always() (per-job names for Appium).
• D5 Version 3.3.0 with a release note in RELEASE.md. Publishing is owner-only.

Notes

• The Raider formatter is registered in helpers/spec_helper.rb rather than .rspec: a command-line --format (as the generated CI uses) replaces .rspec formatters and would silently drop it.
• spec_helper requires digest; allure-ruby-commons 2.28 uses Digest::MD5 without requiring it and crashed the run (exit 1) before results were written.
• Readme gets a Reporting section for RSpec projects.

Verification

• Content suite: 432 examples, 0 failures.
• bundle exec rake integration: 861 examples, 0 failures (~32 s, local Chrome). The RSpec x Selenium and RSpec x Watir end-to-end specs now assert raider-results/run.json (schema_version 1, every example present, exit status unchanged). The e2e helper resolves ruby_raider from the checkout, since the pinned 3.3 is not published yet.

[github-actions]

📝 [rubocop] <Layout/EmptyLinesAroundBlockBody> _{reported by reviewdog 🐶}
Extra empty line detected at block body end.

Suggested change

	end
	end