Guides for Working with Scenes and Checks
For humans and language models writing scene specs and inline checks.
Getting StartedSimple steps for setting up your first actors, scenes and checks, converting old specs, and more.→How Scenetest Works
We've split the test into its two main parts: `scenes` and `checks`.
Scene Orchestration — scripts that simulate user journeys (login, fill form, click submit). Written in spec files. Not concerned with implementation details.
Writing Scene SpecsLearn how to write scene specs that describe user journeys and orchestrate browser interactions.→Building Teams of ActorsDesign teams that mirror your seed data, scale concurrency, and keep scenes reliable.→Integrity Checks — assertion functions like
Writing Inline ChecksUse should(), and failed() on client and with serverCheck() in your application code.→should()andfailed()andserverCheck(), that can run and should pass every time your component or mutation or effect runs. Not concerned with the reason the actor is using the page, just runs every time the page gets used (when deployed in test mode).
API References
For complete documentation on actor methods, selectors, and the text DSL format:
Actor APINavigation, visibility, interaction, scope, conditionals, and coordination.→SelectorsAttribute matching, nested selectors, key selectors, aliases, and sigils.→Text DSL FormatGrammar, .spec.md files, the dsl() method, and macros.→CLI ReferenceThe CLI discovers and runs scene specs, manages browser lifecycle, teams, reports.→