A persona is a detailed representation of a typical system user, combining a name with goals, abilities, background, habits, and other realistic details. Naming the person makes user stories and acceptance scenarios more concrete than generic roles such as “The User” or “The Customer.” section 7.6.5 section 9.2
Use personas to improve shared understanding and executable test data:
- Frame behavior around a recognizable user, making it easier to judge whether a feature serves real-world needs. section 7.6.5
- Replace vague actors in scenarios with named people whose goals and circumstances clarify the expected behavior. section 7.6.5
- Store precise persona data behind a well-known name so scenarios remain readable while test code supplies registration, login, or account details. section 9.2.1
- Represent different credentials and personal details through actors, abilities, notes, and generated traveler data in Serenity/JS tests. section 14.2.3
From generic user to Sam
Instead of “As a user, I want to see my account details,” describe Sam, a stay-at-home dad who monitors expenses on a laptop. A scenario can then state that Sam views his account summary and should see current balances, pending transactions, and available amounts. section 7.6.5
Scenario: Registering online for a new Frequent Flyer account Given Jane is not a Frequent Flyer member When Jane registers for a new account Then she should be sent a confirmation email And she should receive 500 bonus points
Follow a named persona through an online registration scenario, including membership state, confirmation email, and bonus points. section 9.2.1
