Skip to content

docs(migration): coming from Serenity BDD - #227

Merged
shossain786 merged 1 commit into
masterfrom
docs/migration-from-serenity
Oct 30, 2026
Merged

shossain786 merged 1 commit into
masterfrom
docs/migration-from-serenity

Conversation

@shossain786

Copy link
Copy Markdown
Contributor

Closes #127

Adds docs-site/docs/migration/from-serenity.md and a sidebar entry.

  • Maps @Steps / Screenplay to page objects and BaseCucumberSteps; feature files carry over unchanged.
  • Selenium Boot calls (BaseCucumberSteps, BasePage, ScenarioContext, StepLogger, LocatorAssert, retry tags, config keys) checked against the source and existing docs.
  • Reporting section states plainly that Serenity's requirements-level living documentation does not carry over.
  • Serenity-side names (@Steps, @Managed, session variables, serenity.conf keys) come from my knowledge of Serenity, not from this repo, so a reviewer who knows Serenity should check them.

npm run build succeeds. The one broken anchor it reports (junit-xml -> html-report#failure-classification) predates this PR.

🤖 Generated with Claude Code

Maps @Steps/Screenplay to page objects and BaseCucumberSteps, covers
reporting differences, and notes that feature files carry over.

Closes #127

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@shossain786
shossain786 merged commit 1646004 into master Oct 30, 2026
2 checks passed
@shossain786
shossain786 deleted the docs/migration-from-serenity branch October 30, 2026 02:54
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.

docs(migration): coming from Serenity BDD

1 participant