القائمة
ReDBox uses Mocha for integration testing and Bruno for API testing. All integration tests are run within Docker containers managed by docker-compose profiles.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Redbox Testing |
| description | ReDBox uses Mocha for integration testing and Bruno for API testing. All integration tests are run within Docker containers managed by docker-compose profiles. |
ReDBox uses Mocha for integration testing and Bruno for API testing. All integration tests are run within Docker containers managed by docker-compose profiles.
Mocha tests are located in packages/*/test. To run them, they are executed within a Docker environment.
Run all Mocha tests (Development):
npm run test:mocha:mount
This mounts your local code into the test containers, allowing for faster iteration.
Run selected Mocha tests (Development):
RBPORTAL_MOCHA_TESTS="test/unit/services/SolrSearchService.test.js" npm run test:mocha:mount
Provide space-separated test file paths or glob patterns. The bootstrap test is always included.
Run all Mocha tests (CI):
npm run test:mocha
This runs the tests using the portal profile without mounting local code.
Clean up Mocha test resources:
npm run test:mocha:clean
Bruno is used for API testing. Tests are located in test/bruno.
Run Bruno OIDC tests (Development):
npm run test:bruno:oidc:mount
This runs tests specifically for OIDC authentication flows with mounted code.
Run Bruno General tests (Development):
npm run test:bruno:general:mount
This runs a general suite of Bruno tests with mounted code.
Run Bruno tests (CI):
The non-mount variants (e.g. npm run test:bruno:oidc) are intended for CircleCI builds.
Cleanup: Use the corresponding clean command for the test suite you ran:
npm run test:bruno:cleannpm run test:bruno:oidc:cleannpm run test:bruno:general:cleanThese commands utilize Docker Compose profiles to start the necessary services (e.g., redboxportal, keycloak, mongo, solr). The package.json scripts define which profiles and compose files are used for each test suite.
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.