plugin-testing
Manual testing suite for JUCE audio plugins. Features automated test execution, pluginval validation (strictness 10), and structured DAW testing checklists for stability and quality assurance.
Introduction
The plugin-testing skill serves as a specialized manual quality assurance environment for the Plugin Freedom System. While the platform incorporates automatic validation after every implementation stage, this skill enables developers and sound designers to perform deep-dive verification, regression testing, and DAW compatibility checks. It is designed to be invoked manually following bug fixes, system updates, or for thorough pre-release stability assessments.
This utility provides three distinct modes of operation to cover every aspect of the development lifecycle. The Automated mode targets logic and parameter state bugs using the local test suite. The Build + Pluginval mode leverages the industry-standard pluginval tool at strictness level 10 to ensure binary compliance for VST3 and AU formats. The Manual DAW testing mode provides a guided, parameter-specific checklist to ensure sonic performance and interface usability within major digital audio workstations like Ableton Live, Logic Pro, and Reaper.
-
Executes automated test suites to identify crashes and state inconsistencies.
-
Runs pluginval at strictness level 10 to validate VST3 and Audio Unit binary architecture.
-
Generates customized manual DAW testing checklists based on the specific parameter specifications of the plugin.
-
Facilitates regression testing to ensure that recent improvements do not introduce new instabilities.
-
Integrates with the overall plugin-workflow to ensure final builds meet production-ready criteria.
-
Input: Requires a valid plugin name and the selection of a test mode (Automated, Pluginval, or Manual).
-
Constraints: The Tests/ directory must exist for the Automated mode; Pluginval must be pre-installed for Mode 2 execution.
-
Interaction: Follows a decision-gate protocol to prevent testing non-existent or un-implemented plugins.
-
Best Practice: Use Mode 2 (Build + Pluginval) as the primary verification step for all production-bound audio plugins.
-
Error Handling: Acts as a critical checkpoint; if failures are detected, it provides actionable data for the /improve skill to address specific bugs.
Repository Stats
- Stars
- 183
- Forks
- 66
- Open Issues
- 4
- Language
- HTML
- Default Branch
- main
- Sync Status
- Idle
- Last Synced
- Apr 29, 2026, 02:17 PM