Testing¶

EUDIPLO uses Vitest for colocated unit tests and backend end-to-end (E2E) tests. Run focused unit tests while developing, then add the relevant E2E suite when a change affects module wiring, persistence, or a protocol flow.

OIDF Conformance Tests¶

EUDIPLO includes dedicated tests for validating compliance with the OpenID Foundation (OIDF) conformance suite for OID4VCI and OID4VP. These tests ensure that the implementation of OID4VCI (OpenID for Verifiable Credential Issuance) and OID4VP (OpenID for Verifiable Presentations) strictly follows the protocol specifications.

The test are part of the E2E tests that run in the Github Action CI pipeline for a pull request and on the main branch.

E2E Tests¶

Backend E2E tests are stored in apps/backend/test/. They verify the assembled application, including protocol flows and integrations with external services.

The following command will run the E2E tests and also provide a coverage report:

pnpm --filter @eudiplo/backend run test:e2e

It is also accessible via codecov.

Code Quality (SonarCloud)¶

Static analysis and code quality metrics are tracked on SonarCloud.

Scope

The SonarCloud analysis focuses on the backend (apps/backend). The Angular client is excluded from coverage reporting as it is considered optional and does not have E2E test coverage yet.

During writing E2E tests, you can use it in watch mode to automatically re-run tests on file changes:

pnpm --filter @eudiplo/backend run test:e2e:watch

Linting¶

Before pushing code, check linting rules and fix them:

pnpm run lint

The repository's Git pre-push hook also runs the Knip check automatically:

pnpm run knip

Install dependencies with pnpm install to enable the Husky hooks locally.

GitHub Actions¶

Tests run automatically on every push to main or pull request via GitHub Actions.

You can find the workflow config in .github/workflows/ci-and-release.yml.

Running Tests Locally¶

To run all workspace unit tests locally:

pnpm run test

To target the backend or use watch mode:

pnpm --filter @eudiplo/backend run test
pnpm --filter @eudiplo/backend run test:watch

This uses Vitest under the hood, which is configured for NestJS.

Test Coverage¶

The coverage is generated when running the E2E tests.

This generates a report in the /coverage folder. Open coverage/index.html in your browser to view it.

Test Structure¶

Unit tests are located next to their implementation files:

src/
  service/
    my.service.ts
    my.service.spec.ts  <-- Test file

Architecture and dependency-boundary tests also use the .spec.ts suffix, so they run with the same backend unit-test command.