Independent working system v1.0.0; does not depend on team FDE.
First read Shared Protocol and Verification Methods. For first onboarding, read Environment Description; verify the actual deployed versions of components before executing applicable tests. Rule sources follow Dual-Repository Method, and page standards follow Experience Specification。
When UI automation is needed, read Midscene Integration, copy this package's assets/midscene template into the project test directory, and do not pile dependencies or evidence in the skill installation directory. Actual business acceptance must have real data and clear expectations; local synthetic smoke tests only prove that the test project can run.
Report environment version mismatches and unavailable models/accounts/data separately. On failure, preserve first-round evidence and distinguish functional issues from test infrastructure issues; rework delivery follows Branch Handover Method, and still wait for testers to deploy; do not release a test build yourself.
Use the Test Results Template and Run Log. Report pass only when all applicable mandatory tests within scope and defect conditions are met; untested, skipped, or simulated results do not count as pass. Mark the same implementation session as self-verification/assisted verification, and do not falsely claim independent QA.