basercms-unittest

Run and diagnose baserCMS PHPUnit tests in a Docker container.

194|141|Updated Feb 12, 2012
One-click install
npx skills add https://github.com/baserproject/basercms --skill basercms-unittest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: basercms-unittest
Source: https://github.com/baserproject/basercms/tree/main/.agents/skills/basercms-unittest
Command: npx skills add https://github.com/baserproject/basercms --skill basercms-unittest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps developers run, filter, and debug baserCMS unit tests locally without guessing the right Docker command, so regressions and environment issues can be isolated faster.

Core Features & Use Cases

  • Full-suite PHPUnit execution inside the basercms Docker container with log capture for long runs.
  • Single-file and single-method test runs for fast iteration on a specific failure.
  • Lint checks and failure triage guidance to separate application bugs from environment, fixture, or localization issues.
  • Use case: when a plugin test starts failing after a change, this skill helps you reproduce it, narrow it to one test, and inspect the root cause efficiently.

Quick Start

Ask the skill to run the relevant baserCMS PHPUnit test or failure check in the Docker container and summarize the result with the most likely cause.

Frequently Asked Questions about basercms-unittest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run baserCMS unit tests in a Docker container?

To run baserCMS unit tests in Docker, execute the full PHPUnit suite inside the local basercms PHP container with log capture enabled, allowing you to monitor long runs and isolate regressions quickly.

Can I run a single PHPUnit test method for baserCMS?

Yes, you can filter PHPUnit execution to a single test file or method within the baserCMS Docker container, enabling fast iteration on a specific failure without running the entire test suite.

How do I debug failing baserCMS plugin tests after a code change?

Debug failing baserCMS plugin tests by reproducing the failure in Docker, narrowing execution to the specific test, and using log-based triage to separate application bugs from environment or fixture issues.

What is the best way to separate baserCMS test failures caused by environment issues?

The best way to separate environment issues in baserCMS tests is using failure triage guidance and lint checks to distinguish application bugs from localization, fixture, or Docker configuration problems.

Do I need a specific Docker setup to run baserCMS PHPUnit tests?

Yes, you need access to the local basercms PHP container and awareness of the phpunit.xml.dist test suites to execute and diagnose baserCMS unit tests properly within the Docker environment.