tests
v2.2.4Test standard as an installable plugin — the execution-tier split, the test contract, the axes a case space is derived from, factories, matchers and fakes, a JSON failure envelope, and the coverage and mutation gates. Ships a whole-tree audit agent and the config a repository states its own numbers in.
By Roman Maslennikov1 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Oct 6, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install tests for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install tests@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/aquivalabs/BladeForgeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/tests/.
Plugin files
├── .claude-plugin/plugin.json├── skills/apex/SKILL.md└── skills/architecture/SKILL.md
Included Skills2
Use when writing, fixing, or extending an Apex test — a test class for a new or changed Apex class, a negative or bulk path, a `@TestSetup` factory, swapping `System.assertEquals` for `Assert.*`, removing a hardcoded record Id, mocking a `RestRequest` for a `@RestResource`, covering a `WITH USER_MODE` or `System.runAs` path, or updating a test after changing the class under test. Also whenever you create or edit any Apex `.cls`, and when reviewing an Apex test somebody else wrote. Apex only — a test in any other runtime needs `tests:architecture` and not this page.
Use when writing, reviewing, moving, or speeding up a unit test — deciding which execution tier a test file belongs to, what a test must satisfy to be accepted, or how coverage and mutation-score gates apply. Also when a test is slow, flaky, or green while the code under it is wrong.
Plugin manifests1
{
"name": "tests",
"description": "Test standard as an installable plugin — the execution-tier split, the test contract, the axes a case space is derived from, factories, matchers and fakes, a JSON failure envelope, and the coverage and mutation gates. Ships a whole-tree audit agent and the config a repository states its own numbers in.",
"version": "2.2.4",
"keywords": [
"testing",
"unit-tests",
"coverage",
"mutation-testing",
"test-standard",
"vitest"
],
"author": {
"name": "Roman Maslennikov",
"email": "[email protected]"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[tests on Agent Plugins Marketplace](https://pluginsmp.com/plugins/tests)