Pipeline Unit Tests

Enable unit tests for a project component when you want Biztraak to add a dedicated test job to the generated pipeline before security checks and image build.

This page describes the managed GitLab pipeline path, which generates .gitlab-ci.yml. Other source-control integrations use their own pipeline configuration. See Capabilities and Availability.

What this setting does

When Run unit tests in this pipeline is enabled for a project component, Biztraak includes a unit-test stage in the generated .gitlab-ci.yml.

• Runs before security and build so obvious regressions fail early
• Stays component-specific so one service can require tests without forcing every component to use them
• Works with generated pipelines instead of asking you to hand-edit CI every time

When to turn it on

Use this setting when:

• your repository already has a reliable unit test project
• your team expects test failures to block image builds
• the component has a meaningful test suite that should run in CI

Leave it off when:

• the repository does not have a stable test command yet
• the component is still being scaffolded
• the pipeline should stay build-only for now

How Biztraak uses it

Biztraak treats this as a pipeline-generation setting for the project component.

• Enabled: generates the unit test job
• Disabled: omits the unit test job

This keeps the pipeline explicit and avoids guessing whether a repo is ready for tests.

Typical Flow

1. Open your project component settings.
2. Turn on Run unit tests in this pipeline.
3. Save the setting.
4. Regenerate or refresh the project pipeline if needed.
5. Push a commit and confirm the unit-test job appears in the configured pipeline integration.

Related docs

• Build & Deploy (CI/CD)
• Web Services Configuration
• Build Reviews

This setting is best used once a component has a real test command and you want CI to enforce it consistently.