0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-06 19:01:54 +00:00

Files

T

kevinveenbirkenbachandClaude Sonnet 4.6 2457d0e13c docs(playwright): add recording section and remove duplicated requirements

- Add Recording Tests section: Playwright codegen (built-in) and
  playwright-recorder (Docker/X11-based) with usage examples
- Replace duplicated spec/env requirement blocks with links to their
  SPOT pages in docs/agents/files/role/
- Extend Development Procedure to include optional recording step

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-30 10:55:19 +02:00

1.7 KiB

Raw Blame History

Integration Tests

This page is the SPOT for integration testing requirements, framework, and structure. Run integration tests with make test-integration.

Framework

You MUST use Python unittest as the test framework.
Tests MUST live under tests/integration/.
Mirror the source tree structure used for unit tests.

When to Write

You MUST add or update integration tests for every *.py file you touch when the change affects behavior across module or runtime boundaries.
Write an integration test when the behavior you are verifying depends on two or more components working together — for example, a lookup plugin reading from real group_vars or a filter interacting with an Ansible variable structure.

Requirements

You MUST NOT mock collaborators that are part of the integration boundary being tested. The point is to verify real interaction.
You MUST NOT write tests that only assert a file contains a string.
You MUST NOT write tests only for non-executable files such as .yml or .j2. Test the behavior that consumes them.
You SHOULD keep each test focused on one integration boundary.
You SHOULD test realistic inputs that match what Ansible would pass at runtime.
You MAY use unittest.mock to stub out external services or filesystem state that is genuinely outside the integration scope.

How to Create

Identify the integration boundary (e.g. lookup plugin + group_vars variable loading).
Create the matching test file under tests/integration/ if it does not exist.
Subclass unittest.TestCase.
Use realistic inputs. Build hypotheses about cross-component behavior before writing assertions.
Run make test-integration and verify all tests pass.

1.7 KiB Raw Blame History