# How to Find Plugins for Testing and QA in the Claude Plugin Marketplace > Discover testing and QA plugins in the Claude plugin marketplace. Use the CLI or web UI to find tools like TestDino. Install effortlessly with claude plugin install. - Repository: [Anthropic/claude-plugins-community](https://github.com/anthropics/claude-plugins-community) - Tags: how-to-guide - Published: 2026-09-08 --- **Use the `claude plugin marketplace list` command or visit the web UI to browse available tools, then search for keywords like "test", "QA", or "TestDino" to locate quality assurance plugins that can be installed via `claude plugin install @claude-community`.** The Claude Plugin Marketplace aggregates community-contributed extensions that enhance Claude Code and Claude Cowork with specialized capabilities. For teams looking to streamline quality assurance workflows, finding the right testing plugins within the `anthropics/claude-plugins-community` repository can significantly improve automated and manual test management directly from the command line. ## Browsing the Claude Plugin Marketplace You can explore available plugins through two interfaces. The CLI provides direct access from your terminal, while the web UI offers a visual browsing experience. ### Using the CLI Interface Run the following command to display all available marketplace entries: ```bash claude plugin marketplace list ``` This command queries the marketplace catalog defined in [`.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json) and returns a list of installable plugins, including testing tools like TestDino. ### Using the Web Interface Alternatively, navigate to in your browser. The web interface provides real-time filtering and detailed plugin descriptions without requiring terminal access. ## Searching for Testing and QA Plugins Once you've opened the marketplace, filter for quality assurance tools using specific keywords. ### Keyword Search Strategies Enter terms such as **"test"**, **"testing"**, **"QA"**, **"automated tests"**, or **"manual testing"** into the search bar. The marketplace indexes plugin metadata and surfaces relevant results like TestDino, which provides comprehensive Playwright test management. ### CLI Search Commands From the command line, you can narrow results by using the search subcommand: ```bash claude plugin marketplace search test ``` This filters the [`marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/marketplace.json) entries to show only testing-related contributions. ## Installing Testing Plugins After locating a suitable QA plugin, you must add it to your marketplace registry and then install it to activate its skills. ### Adding Plugins to Your Registry Before installation, register the plugin source using the `add` command. For the TestDino testing suite: ```bash claude plugin marketplace add testdino-hq/TestDino-Plugins ``` To add the general community repository itself: ```bash claude plugin marketplace add anthropics/claude-plugins-community ``` ### Installing and Activating Plugins Install a specific plugin version to make its skills available in Claude: ```bash claude plugin install testdino-hq/TestDino-Plugins@claude-community ``` Once installed, you can execute testing workflows. For example, to list recent automated test runs: ```bash claude run testdino-runs list_testruns --hours 1 ``` ## Exploring Plugin Documentation and Skills Each testing plugin includes structured documentation and skill definitions that outline available commands. ### README and Configuration Files The primary documentation resides in [`testdino/README.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/README.md) within the repository, containing installation instructions and feature overviews. Machine-readable metadata exists in [`.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json), which catalogs all community plugins with searchable tags for "test" and "qa". ### Skill Definitions Testing capabilities are organized into individual skill directories. The TestDino plugin defines multiple QA workflows: - [`testdino/skills/testdino-runs/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-runs/SKILL.md) – Defines commands for listing and inspecting automated test runs - [`testdino/skills/testdino-manual-tests/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-manual-tests/SKILL.md) – Contains specifications for creating, updating, and browsing manual QA test cases and suites - [`testdino/skills/testdino-audit/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-audit/SKILL.md) – Documents the Playwright test audit functionality via the TestDino MCP server These files specify the exact command syntax and parameters for each testing operation. ## Summary - Use `claude plugin marketplace list` to browse or `claude plugin marketplace search test` to filter for testing tools - Add plugins with `claude plugin marketplace add /` before installing them - Install testing plugins using `claude plugin install @claude-community` to activate QA capabilities - Reference [`testdino/README.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/README.md) and individual [`SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/SKILL.md) files in `/skills/` directories for detailed command specifications - Execute testing workflows through `claude run` commands after installation ## Frequently Asked Questions ### What is the TestDino plugin and how does it help with QA? TestDino is a comprehensive testing plugin available in the Claude Plugin Marketplace that manages both automated Playwright tests and manual QA processes. According to the [`testdino/README.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/README.md) file in the `anthropics/claude-plugins-community` repository, it provides skills for listing test runs, debugging test cases, and auditing applications through an MCP server integration. ### How do I add a plugin from the community marketplace versus installing it? Adding a plugin registers its source in your local marketplace registry using `claude plugin marketplace add `, which makes the plugin available for selection. Installing a plugin using `claude plugin install @claude-community` actually downloads and activates the plugin's skills within Claude Code, making commands like `claude run testdino-runs list_testruns` executable. ### Where can I find the skill definitions for testing plugins? Skill definitions are located in `/skills/` subdirectories within each plugin folder. For TestDino, the key files are [`testdino/skills/testdino-runs/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-runs/SKILL.md) for automated testing, [`testdino/skills/testdino-manual-tests/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-manual-tests/SKILL.md) for manual QA workflows, and [`testdino/skills/testdino-audit/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-audit/SKILL.md) for audit capabilities. These markdown files specify command parameters and usage examples. ### Can I search for plugins directly from the CLI? Yes, use the `claude plugin marketplace search ` command to filter available plugins without opening the web UI. For testing tools, running `claude plugin marketplace search test` queries the [`.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json) file and returns only plugins with testing-related metadata tags.