How do you document automation tests for QA?

Documentation creates accountability and enables consistent testing:

Test case documentation: Describe the scenario being tested. Define input conditions and test data. Specify expected behavior and results. Include steps to reproduce the test.

Results recording: Actual outcome versus expected outcome. Pass/fail status with reasoning. Screenshots or logs as evidence. Issues discovered with severity rating.

Test coverage matrix: Map all automation paths and conditions. Track which have been tested. Identify gaps in coverage. Prioritize testing of critical paths.

Regression testing: Document tests to repeat after changes. Maintain library of test scenarios. Update documentation when automation changes.

Sign-off process: Define who approves test completion. Require sign-off before production launch. Archive documentation for future reference.

Undocumented testing is unrepeatable testing. When problems arise, you need to know what was verified.