odoo-test

odoo-test is a command for Claude Code from ahmed-lakosha/odoo-plugins. It costs 19 tokens per session (457 once invoked), scanned A, original, MIT.

A command toolkit for testing Odoo modules, including tests that exercise models, web requests, and full browser flows. It can also create mock data and inspect code coverage, which shows how much code tests exercise.

In plain words
What is it for?
Generating and running unit-style and browser tests, creating mock records, checking coverage, and running Playwright end-to-end tests.
Why use it?
It reduces the manual work of creating test scaffolding, test data, test runs, and coverage checks for Odoo modules.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the odoo-test-plugin plugin — 1 skill, 1 command shipped together

Good fit Generating and running unit-style and browser tests, creating mock records, checking coverage, and running Playwright end-to-end tests.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ahmed-lakosha/odoo-plugins
Claude Code
/plugin install odoo-test-plugin

Made for: Claude Code.

Or install odoo-test-plugin, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for odoo-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/ahmed-lakosha/odoo-plugins/odoo-test/github.svg)](https://agentmods.dev/commands/ahmed-lakosha/odoo-plugins/odoo-test)
Your own site
<a href="https://agentmods.dev/commands/ahmed-lakosha/odoo-plugins/odoo-test"><img src="https://agentmods.dev/badge/commands/ahmed-lakosha/odoo-plugins/odoo-test/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for odoo-test

Your own site · 80×15
<a href="https://agentmods.dev/commands/ahmed-lakosha/odoo-plugins/odoo-test"><img src="https://agentmods.dev/badge/commands/ahmed-lakosha/odoo-plugins/odoo-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 457 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00457
Opus 5 $0.00010 $0.00229
Sonnet 5 $0.00004 $0.00091
Haiku 4.5 $0.00002 $0.00046

Measured 9d ago against content hash 7b6caad49506, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

odoo-test scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

odoo-test-plugin/commands/odoo-test.md · 47 lines

What it actually says

/odoo-test [sub-command] [args...]

Parse the first token of $ARGUMENTS and route:

Token Action
(empty) Show help + offer full workflow (generate > run > coverage)
generate Generate TransactionCase/HttpCase test skeleton
data Generate mock data factory for setUp
run Run test suite with colored output
coverage Scan for untested methods + coverage %
e2e Generate/run Playwright E2E tests
(other) Treat as module name, run full workflow
/odoo-test                              Show help + offer full workflow
/odoo-test generate <model> [module]    Generate test skeleton
/odoo-test data <model> [--count N]     Generate mock data factory
/odoo-test run <module> [--tags X]      Run test suite
/odoo-test coverage <module>            Coverage analysis
/odoo-test e2e <module> [--url X]       Playwright E2E tests

Execution

Use the odoo-test skill for:

  • Test generation patterns (TransactionCase, HttpCase, SavepointCase)
  • Mock data factory patterns (field-type-aware generation)
  • Test execution with config/database auto-detection
  • Coverage analysis methodology (static method comparison)
  • E2E test scaffolding (Playwright + page objects)
  • Azure DevOps CI integration patterns

Scripts at ${CLAUDE_PLUGIN_ROOT}/odoo-test/scripts/:

  • test_generator.py - Generate test skeletons from models
  • mock_data_factory.py - Generate realistic test data
  • test_runner.py - Execute test suites with colored output
  • coverage_reporter.py - Test coverage analysis
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 47 lines · 19 tokens per session scan A 7b6caad49506

Subscribe to this mod's changes

odoo-test is a command published in the GitHub repository ahmed-lakosha/odoo-plugins (74 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 457 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.