Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | # Regression Testing |
| 2 | |
| 3 | ## Workflow |
| 4 | |
| 5 | 1. Reproduce the bug or identify the failing assertion/CI job. |
| 6 | 2. Trace the root cause in the smallest affected module. |
| 7 | 3. Patch the cause, not only the symptom. |
| 8 | 4. Add or update a regression test in the existing test area for that feature. |
| 9 | 5. Run the focused test first, then the smallest broader check that covers the touched surface. |
| 10 | |
| 11 | ## TypeScript Tests |
| 12 | |
| 13 | - Tests usually live under `ts/packages/<package>/test/`. |
| 14 | - Use Vitest patterns already present in the package. |
| 15 | - Prefer adding to an existing feature test file over creating one-off regression files. |
| 16 | - Useful commands: |
| 17 | |
| 18 | ```bash |
| 19 | pnpm --filter @composio/<package> test |
| 20 | pnpm --filter @composio/<package> typecheck |
| 21 | pnpm test |
| 22 | ``` |
| 23 | |
| 24 | ## Python Tests |
| 25 | |
| 26 | - Tests live under `python/tests/`. |
| 27 | - Shared fixtures live in `python/tests/conftest.py`. |
| 28 | - Use pytest markers that match the affected package or provider. |
| 29 | - Useful commands from `python/`: |
| 30 | |
| 31 | ```bash |
| 32 | make chk |
| 33 | make tst |
| 34 | make snt |
| 35 | pytest tests/test_<feature>.py |
| 36 | ``` |
| 37 | |
| 38 | ## PR Notes |
| 39 | |
| 40 | In the PR body, name the bug, the regression test, and the verification command output. If a test is intentionally skipped, say why. |