odoo-ps/ps-ai-skills · Archived

test_skill

AI Test Failure Resolution Rules for Odoo development.

Hot #2307

Installation

$ npx skills add odoo-ps/ps-ai-skills --skill test_skill

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from odoo-ps/ps-ai-skills · top by installs.

npx skills add odoo-ps/ps-ai-skills

Browse all from odoo-ps/ps-ai-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,255 B
  • docs SUMMARY.md 72 B

History

  1. First recorded snapshot · 7 installs

SKILL.md

Odoo Test Failure Resolution Rules

This skill provides mandatory rules for handling test failures during AI-assisted testing.

🧪 AI TEST FAILURE RESOLUTION RULES

When running Odoo tests, analyze any failures and apply exactly one of the three rules below — nothing else:

  1. RULE 1 — Custom test fails:

The custom module code is broken (e.g. upgrade logic did not preserve the expected workflow). → Fix the custom module CODE so the workflow is correct again. Never weaken or skip the test.

  1. RULE 2 — Standard Odoo test fails because of our custom code:

Our changes altered a workflow or model that a standard test relied on. → Monkey-patch the standard test from within the custom module so it aligns with the new workflow. Never modify standard Odoo files. Never make the test trivially pass by removing assertions.

  1. RULE 3 — Standard Odoo test fails for an unrelated reason:

Do nothing. Skip it and move on.

After applying a fix, re-run the tests and repeat until all Rule-1 and Rule-2 failures are resolved. Finish with a summary of every change made and which rule justified it.