Make the expectation explicit
Connect the available AuraCheck MCP server and ask Claude Code to inspect the project. Request a proposed journey with setup, actions, and assertions before allowing a run.
Put it into practice
After execution, ask which assertions passed, what evidence was available, and what remains untested. If the environment failed to load, report a blocked test instead of inferring application behavior.
Try this on your next release
Choose one journey, define the expected result, and inspect the evidence from a completed run. Expand the suite after the first test is useful.