mcpField
P
probat-testing

probat-testing

github.com/thalysjuvenalTesting & quality19148 installsUpdated 6w ago
Repository

About probat-testing

probat-testing is a skill for writing and running ProBat unit, functional, and integration tests for TLPP source files, including tests of legacy `.prw` code. It documents fixtures, annotations, assertions, and execution through the REST API or VSCode extension.

Key features

  1. 01Fixture and test method patterns
  2. 02Setup and teardown annotations
  3. 03ProBat assertion functions
  4. 04Class-based test lifecycle
  5. 05REST API and VSCode execution guidance

Use cases

  1. 01Create a ProBat test fixture
  2. 02Add tests for a routine
  3. 03Configure setup and teardown logic
  4. 04Understand test discovery and execution

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/thalysjuvenal/advpl-specialist --skill probat-testing

After installing, type/probat-testingin Claude Code to confirm it loaded.

Bundled filespatterns-unit-tests.mdreference.md

Details

From the project README

ProBat Testing (TLPP)

This skill covers ProBat, the native unit/functional/integration testing engine of tlppCore, used exclusively with TLPP (.tlpp) source files -- even when the code under test is legacy .prw. It covers the required #include "tlpp-probat.th", the test.<module> namespace convention, the full annotation set (@TestFixture, @Test, @Setup, @TearDown, @OneTimeSetUp, @OneTimeTearDown, @Skip, @ErrorLog), the tlpp.probat assertion functions, the class-based execution lifecycle, and SKIPASSERT for conditional assertion skipping.

Activate this skill when the user wants to create a new ProBat test fixture, add test methods to cover a routine, set up setup/teardown logic, or understand how ProBat discovers and executes tests (via REST API or the VSCode extension). Concrete test-writing templates live in the sibling patterns file.

It does not cover generating the production TLPP code being tested (see advpl-code-generation), reviewing code quality outside of tests (see advpl-code-review), or writing embedded SQL used inside test fixtures (see embedded-sql).

Reference fileRead when
reference.mdAlways -- includes, namespace convention, annotations, assertion function reference, execution lifecycle, and how tests are run
patterns-unit-tests.mdWriting a concrete ProBat test fixture and need ready-to-adapt templates/patterns

Comments

Markdown supported