Change email address
Two scenarios share the same Given setup, so the report groups them under one background.
The test
Section titled “The test”import { story } from 'executable-stories-vitest';import { describe, it } from 'vitest';
describe("Feature: Account settings", () => { it("Change email address", ({ task }) => { story.init(task); story.given("the user account exists"); story.given("the user is logged in"); story.then("a verification email should be sent"); story.then('the email status should be "pending verification"'); });});import { story } from 'executable-stories-jest';
describe("Feature: Account settings", () => { it("Change email address", () => { story.init(); story.given("the user account exists"); story.given("the user is logged in"); story.then("a verification email should be sent"); story.then('the email status should be "pending verification"'); });});import { test } from '@playwright/test';import { story } from 'executable-stories-playwright';
test.describe("Feature: Account settings", () => { test("Change email address", async ({}, testInfo) => { story.init(testInfo); story.given("the user account exists"); story.given("the user is logged in"); story.then("a verification email should be sent"); story.then('the email status should be "pending verification"'); });});import { story } from 'executable-stories-cypress';
describe("Feature: Account settings", () => { it("Change email address", () => { story.init(); story.given("the user account exists"); story.given("the user is logged in"); story.then("a verification email should be sent"); story.then('the email status should be "pending verification"'); });});What the report renders
Section titled “What the report renders”### ✅ Change email address
- **Given** the user account exists- **And** the user is logged in- **Then** a verification email should be sent- **And** the email status should be "pending verification"