Agent skill

Odoo Automated Tests

by sickn33 in sickn33/agentic-awesome-skills

Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests.

MITAuto-check passedTesting & QA

Install Odoo Automated Tests

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-automated-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/odoo-automated-tests .claude/skills/odoo-automated-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "odoo-automated-tests" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-automated-tests into .claude/skills/odoo-automated-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-automated-tests", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-automated-tests

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-automated-tests --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/odoo-automated-tests .agents/skills/odoo-automated-tests && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "odoo-automated-tests" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-automated-tests into .agents/skills/odoo-automated-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-automated-tests", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-automated-tests --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/odoo-automated-tests .cursor/skills/odoo-automated-tests && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "odoo-automated-tests" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-automated-tests into .cursor/skills/odoo-automated-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-automated-tests", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/odoo-automated-tests

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-automated-tests --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/odoo-automated-tests .gemini/skills/odoo-automated-tests && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "odoo-automated-tests" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-automated-tests into .gemini/skills/odoo-automated-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-automated-tests", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-automated-tests

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/odoo-automated-tests .github/skills/odoo-automated-tests && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "odoo-automated-tests" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-automated-tests into .github/skills/odoo-automated-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-automated-tests", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-automated-tests --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/odoo-automated-tests .opencode/skills/odoo-automated-tests && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "odoo-automated-tests" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-automated-tests into .opencode/skills/odoo-automated-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-automated-tests", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: odoo-automated-tests
GitHub stars: 47k
Used in: 2 other repos
Token cost: ~1.3k tokens
SKILL.md length: 325 words
Files: 1
Skills in repo: 1,497
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests.

Works in 3 steps: Activate: Mention @odoo-automated-tests… → Generate: Get complete test class code… → Run: Get the exact odoo CLI command to…
Tasks that involve Test data and fixtures
SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Odoo Automated Tests is an agent skill from sickn33/agentic-awesome-skills. Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests. Covers test data setup, mocking, and CI integration.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test data and fixtures and Unit testing. It works with Odoo. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

Tasks that involve Test data and fixtures
Tasks that involve Unit testing

Example prompts

“/odoo-automated-tests”

Requirements

Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Activate: Mention @odoo-automated-tests and describe the feature to test.
Generate: Get complete test class code with setup, teardown, and assertions.
Run: Get the exact odoo CLI command to execute your tests.

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Odoo Automated Tests loads about 1.3k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 325 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~41
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 325 words, ~1,281 tokens.

Download SKILL.mdSave it as .claude/skills/odoo-automated-tests/SKILL.md (or your agent's skills folder).

name: odoo-automated-tests
description: Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests. Covers test data setup, mocking, and CI integration.
risk: safe
source: self
date_added: 2026-09-04

Odoo Automated Tests

Overview

Odoo has a built-in testing framework based on Python's unittest. This skill helps you write TransactionCase unit tests, HttpCase integration tests, and JavaScript tour tests. It also covers running tests in CI pipelines.

When to Use This Skill

Writing unit tests for a custom model's business logic.
Creating an HTTP test to verify a controller endpoint.
Debugging test failures in a CI pipeline.
Setting up automated test execution with --test-enable.

How It Works

Activate: Mention @odoo-automated-tests and describe the feature to test.
Generate: Get complete test class code with setup, teardown, and assertions.
Run: Get the exact odoo CLI command to execute your tests.

Examples

Example 1: TransactionCase Unit Test (Odoo 15+ pattern)

python

# tests/test_hospital_patient.py
from odoo.tests.common import TransactionCase
from odoo.tests import tagged
from odoo.exceptions import ValidationError

@tagged('post_install', '-at_install')
class TestHospitalPatient(TransactionCase):

    @classmethod
    def setUpClass(cls):
        # Use setUpClass for performance — runs once per class, not per test
        super().setUpClass()
        cls.Patient = cls.env['hospital.patient']
        cls.doctor = cls.env['res.users'].browse(cls.env.uid)

    def test_create_patient(self):
        patient = self.Patient.create({
            'name': 'John Doe',
            'doctor_id': self.doctor.id,
        })
        self.assertEqual(patient.state, 'draft')
        self.assertEqual(patient.name, 'John Doe')

    def test_confirm_patient(self):
        patient = self.Patient.create({'name': 'Jane Smith'})
        patient.action_confirm()
        self.assertEqual(patient.state, 'confirmed')

    def test_empty_name_raises_error(self):
        with self.assertRaises(ValidationError):
            self.Patient.create({'name': ''})

    def test_access_denied_for_other_user(self):
        # Test security rules by running as a different user
        other_user = self.env.ref('base.user_demo')
        with self.assertRaises(Exception):
            self.Patient.with_user(other_user).create({'name': 'Test'})

setUpClass vs setUp: Use setUpClass (Odoo 15+) for shared test data. It runs once per class and is significantly faster than setUp which re-initializes for every single test method.

Example 2: Run Tests via CLI

bash

# Run all tests for a specific module
./odoo-bin --test-enable --stop-after-init -d my_database -u hospital_management

# Run only tests tagged with a specific tag
./odoo-bin --test-enable --stop-after-init -d my_database \
  --test-tags hospital_management

# Run a specific test class
./odoo-bin --test-enable --stop-after-init -d my_database \
  --test-tags /hospital_management:TestHospitalPatient

Example 3: HttpCase for Controller Testing

python

from odoo.tests.common import HttpCase
from odoo.tests import tagged

@tagged('post_install', '-at_install')
class TestPatientController(HttpCase):

    def test_patient_page_authenticated(self):
        # Authenticate as a user, not with hardcoded password
        self.authenticate(self.env.user.login, self.env.user.login)
        resp = self.url_open('/hospital/patients')
        self.assertEqual(resp.status_code, 200)

    def test_patient_page_redirects_unauthenticated(self):
        # No authenticate() call = public/anonymous user
        resp = self.url_open('/hospital/patients', allow_redirects=False)
        self.assertIn(resp.status_code, [301, 302, 403])

Best Practices

✅ Do: Use setUpClass() with cls.env instead of setUp() — it is dramatically faster for large test suites.
✅ Do: Use @tagged('post_install', '-at_install') to run tests after all modules are installed.
✅ Do: Test both the happy path and error conditions (ValidationError, AccessError, UserError).
✅ Do: Use self.with_user(user) to test access control without calling sudo().
❌ Don't: Use a production database for tests — always use a dedicated test database.
❌ Don't: Rely on test execution order — each TransactionCase test is rolled back in isolation.
❌ Don't: Hardcode passwords in HttpCase.authenticate() — use self.env.user.login or a fixture user.

Limitations

JavaScript tour tests require a running browser (via phantomjs or Chrome headless) and a live Odoo server — not covered in depth here.
HttpCase tests are significantly slower than TransactionCase — use them only for controller/route verification.
Does not cover mocking external services (e.g., mocking an SMTP server or payment gateway in tests).
Test isolation is at the transaction level, not database level — tests that commit data (e.g., via cr.commit()) can leak state between tests.

Files

Just SKILL.md in skills/odoo-automated-tests of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 2 other repositories

We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Odoo Automated Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Odoo Automated Tests compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Odoo Automated Tests this skillsickn33/agentic-awesome-skills	47k	2 repos	~1.3k	Automated safety check: Pass	MIT	yesterday
Jest Testing PatternsChrisWiles/claude-code-showcase	6.1k	7 repos	~1.5k	Automated safety check: Pass	None	9 mo ago
RTK Filter TDD in Rustrtk-ai/rtk	83k	—	~1.9k	Automated safety check: Notes	Apache-2.0	yesterday
Aspire Integration TestingDevBetterCom/DevBetterWeb	157	2 repos	~2.3k	Automated safety check: Pass	None	7 days ago
Data Client React Testingreactive/data-client	2k	—	~1.5k	Automated safety check: Pass	Apache-2.0	today
Robotics Testingarpitg1304/robotics-agent-skills	369	—	~4.7k	Automated safety check: Pass	Apache-2.0	1 mo ago

Similar skills

Jest Testing Patterns
ChrisWiles/claude-code-showcase
Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.
6.1k GitHub starsUsed in 7 repos~1.5k tokens
Testing & QAAuto-check passed
RTK Filter TDD in Rust
rtk-ai/rtk
Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.
83k GitHub stars~1.9k tokensUpdated yesterday
Testing & QAAuto-check: notes
Aspire Integration Testing
DevBetterCom/DevBetterWeb
Write integration tests using .NET Aspire's testing facilities with xUnit.
157 GitHub starsUsed in 2 repos~2.3k tokens
Testing & QAAuto-check passed
Data Client React Testing
reactive/data-client
Test @data-client/react with renderDataHook and mountDataClient - jest unit tests, fixtures, interceptors, MockResolver, mock responses, nock HTTP mocking, fake timers for polling/subscription…
2k GitHub stars~1.5k tokensUpdated today
Testing & QAAuto-check passed
Robotics Testing
arpitg1304/robotics-agent-skills
Testing strategies, patterns, and tools for robotics software.
369 GitHub stars~4.7k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
ClickUp CLI Testing
krodak/clickup-cli
Explains how to run and extend the clickup-cli tests: unit tests with a mocked client, e2e tests against a real ClickUp workspace, and the fixture data they rely on.
123 GitHub stars~1.4k tokensUpdated 4 days ago
Testing & QAAuto-check: notes

Questions about Odoo Automated Tests

What does Odoo Automated Tests do?

Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests. Odoo Automated Tests is an agent skill from sickn33/agentic-awesome-skills. Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests.

When should I use Odoo Automated Tests?

Odoo Automated Tests fits situations like: tasks that involve Test data and fixtures; tasks that involve Unit testing.

How do I install Odoo Automated Tests in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a claude-code`. Or copy the skill folder (skills/odoo-automated-tests in sickn33/agentic-awesome-skills) into .claude/skills/odoo-automated-tests in your project. Claude Code loads it when a task matches its description.

How do I install Odoo Automated Tests in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a codex`. Or copy the skill folder (skills/odoo-automated-tests in sickn33/agentic-awesome-skills) into .agents/skills/odoo-automated-tests in your project. Codex loads it when a task matches its description.

Can I use Odoo Automated Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill odoo-automated-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/odoo-automated-tests, .gemini/skills/odoo-automated-tests, .github/skills/odoo-automated-tests and .opencode/skills/odoo-automated-tests in your project.

What does Odoo Automated Tests need to run?

SKILL.md names no scripts, command-line tools or credentials: Odoo Automated Tests is instructions for the agent only. Our summary lists: Python 3.

Does Odoo Automated Tests access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Odoo Automated Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Odoo Automated Tests use?

Odoo Automated Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Odoo Automated Tests use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Odoo Automated Tests?

Skills that share tags, products or a category with Odoo Automated Tests: Jest Testing Patterns (ChrisWiles/claude-code-showcase, 6.1k stars), RTK Filter TDD in Rust (rtk-ai/rtk, 83k stars), Aspire Integration Testing (DevBetterCom/DevBetterWeb, 157 stars) and Data Client React Testing (reactive/data-client, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Odoo Automated Tests?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Odoo Automated Tests

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Odoo Automated Tests

Overview

When to Use This Skill

How It Works

Examples

Example 1: TransactionCase Unit Test (Odoo 15+ pattern)

Example 2: Run Tests via CLI

Example 3: HttpCase for Controller Testing

Best Practices

Limitations

Files

Used in 2 other repositories

Compare with similar skills

Similar skills

More from sickn33/agentic-awesome-skills

Related

Questions about Odoo Automated Tests