Menü
Ensure every new service or controller gets Mocha or Bruno coverage by analyzing the implemented code and writing integration tests.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
| name | Redbox Test Verification |
| description | Ensure every new service or controller gets Mocha or Bruno coverage by analyzing the implemented code and writing integration tests. |
Use this skill whenever new business logic or routes are merged so the functionality can be verified by automated tests before release.
packages/redbox-core/src/services (for services) or packages/redbox-core/src/controllers plus config/routes (for routes) to understand the happy path, dependencies, and any edge cases the feature must cover.packages/redbox-core/src/services, add an integration test under typescript/test/integration/services. Prefer naming the file after the service (e.g., MyService.test.ts).typescript/test/integration/services/helpers as needed, but focus on exercising the whole service flow (setup data, call the method or endpoint, then read back the data it should have created/updated).typescript/test/unit/services/index.ts helpers if required.test/bruno that hits the HTTP endpoint through the normal request pipeline.test/bruno/general) and ensure the new file is wired into the test/bruno/run scripts if needed.npm run test:mocha:mount (local iteration) or npm run test:mocha (CI) to build confidence that the service behaves as expected.npm run test:bruno:general:mount (or the appropriate profile) and ensure the new route passes before finishing.support/wiki/redbox-core.md or support/wiki/Redbox-Loader.md).Basierend auf der SOC-Berufsklassifikation
ReDBox uses embedded Angular applications within EJS views instead of a single SPA. Each feature is often its own Angular project.
Angular services in ReDBox typically extend `HttpClientService` to handle base URLs, configuration, and CSRF protection.
ReDBox controllers live in `@researchdatabox/redbox-core` and are surfaced to Sails.js through generated shims.
Create detailed feature designs, implementation plans, and task lists for ReDBox/Redbox features that use Waterline models, services, webservice (REST) controllers, ajax controllers, embedded Angular apps, views, and navigation config. Use when asked to design/plan a feature or produce a task list for this stack, especially when explicit sections, non-SPA Angular patterns, and interleaved tests are required.
Review completed ReDBox feature implementations against a growing ruleset and emit structured issues for agent remediation.
Build or update ReDBox form field components end-to-end across Angular form rendering and sails-ng-common config typing/visitor infrastructure. Use when creating a new form component class/model, adding component config properties, wiring component dictionaries, handling config migration/template extraction, or adding form-component tests.
