agentmods.dev

magento-testing

magento-testing is a skill for Claude Code from OrcaQubits/agentic-commerce-skills-plugins. It costs 46 tokens per session (932 once invoked), scanned A, original, MIT.

A testing guide for Magento 2, Adobe's e-commerce platform. It covers PHPUnit tests for individual code units, integration tests with Magento, functional browser tests, and API tests.

In plain words
What is it for?
Use it to add test coverage to Magento modules, investigate failures, and prepare unit, integration, functional, or API tests for a CI pipeline.
Why use it?
It helps you choose the right kind of test and provides patterns for checking modules without relying on guesswork. It also covers running tests in continuous integration, which automatically checks code changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the magento2-commerce plugin — 19 skills, 1 agent shipped together

not rated 39repo 3d ago A scan 46 tokens original MIT

Good fit Use it to add test coverage to Magento modules, investigate failures, and prepare unit, integration, functional, or API tests for a CI pipeline.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orcaqubits/agentic-commerce-skills-plugins/magento-testing
View source ↗ OrcaQubits/agentic-commerce-skills-plugins
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add OrcaQubits/agentic-commerce-skills-plugins --skill magento-testing
Clone the repo
git clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-plugins

Made for: Claude Code.

Or install magento2-commerce, the plugin that ships this one along with the rest of its 19 skills, 1 agent.

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 magento-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-testing/github.svg)](https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/magento-testing)
Your own site
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/magento-testing"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-testing/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 magento-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/magento-testing"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/magento-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 932 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.00046 $0.00932
Opus 5 $0.00023 $0.00466
Sonnet 5 $0.00009 $0.00186
Haiku 4.5 $0.00005 $0.00093

Measured 3d ago against content hash 62a62fb210d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-17, from the pricing page.

Security

Grade A, and why

magento-testing 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 3d 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.

magento2-commerce/skills/magento-testing/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Magento 2 Testing

Before writing code

Fetch live docs:

  1. Web-search site:developer.adobe.com commerce testing for testing overview
  2. Fetch https://developer.adobe.com/commerce/testing/functional-testing-framework/ for MFTF guide
  3. Web-search site:developer.adobe.com commerce php development test for unit/integration test patterns

Testing Layers

Unit Tests

Purpose: Test individual classes in isolation.

  • Location: Test/Unit/ within the module
  • Config: dev/tests/unit/phpunit.xml.dist
  • Run: vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist app/code/VendorName/ModuleName/Test/Unit/
  • Mock all dependencies with PHPUnit mocks or createMock()
  • No Magento bootstrap — pure PHP unit testing
  • Fast execution, no database or filesystem dependencies

Integration Tests

Purpose: Test module interactions with the Magento framework.

  • Location: Test/Integration/ or dev/tests/integration/
  • Config: dev/tests/integration/phpunit.xml.dist
  • Run: vendor/bin/phpunit -c dev/tests/integration/phpunit.xml.dist
  • Uses Magento application bootstrap — real DI, real database
  • @magentoDbIsolation enabled — rolls back DB changes after each test
  • @magentoAppArea — sets the application area (frontend, adminhtml)
  • @magentoConfigFixture — sets config values for the test
  • @magentoDataFixture — loads test data
  • Slower but tests real interactions

MFTF (Magento Functional Testing Framework)

Purpose: End-to-end browser tests.

  • XML-based test definitions (not PHP)
  • Converts to Codeception PHP tests
  • Uses Selenium WebDriver for browser automation
  • Allure reporting for results
  • Location: Test/Mftf/Test/, Test/Mftf/ActionGroup/, Test/Mftf/Page/, Test/Mftf/Section/
  • Run: vendor/bin/mftf run:test <TestName>
  • Tests complete user workflows (add to cart, checkout, admin operations)

API Functional Tests

Purpose: Test REST and SOAP API endpoints.

  • Location: dev/tests/api-functional/
  • Config: dev/tests/api-functional/phpunit_rest.xml.dist
  • Tests API request/response contracts
  • Verifies authentication, authorization, and data integrity

Read the full file on GitHub · 106 lines

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. 3d ago First seen · 106 lines · 46 tokens per session scan A 62a62fb210d9

Subscribe to this mod's changes

magento-testing is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 932 once invoked, about $0.0002 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-09-15.

E2E testingMagentoTestingUnit testinga2aacpagentic-commerceucpwebmcp
Related

Other skills, from other repositories

archestra-dev-testing

Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.

archestra-ai/archestra · 68 tokens

archestra-dev-backend-tests

Use when writing or modifying Archestra backend unit tests (platform/backend/src//.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.

archestra-ai/archestra · 46 tokens

archestra-dev-e2e

Use when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.

archestra-ai/archestra · 45 tokens

harn-testing

Test owning interfaces, canonical paths, liveness, replay, and stochastic quality at the right altitude.

burin-labs/harn · 24 tokens

testing-patterns

Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.

softspark/ai-toolkit · 52 tokens

JMeter Load Testing

Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.

PramodDutta/qaskills · 32 tokens