Skip to content

STORY: Standardize Java unit and integration test phases #6

Closed

Description

@ramioooz

Parent: EPIC: Testing & Quality

Objective

Standardize how Java services separate fast unit tests from Spring/Testcontainers integration tests so CI can run clear test stages.

Scope

  • Define naming conventions for unit and integration tests.
  • Configure Maven Surefire for unit tests.
  • Configure Maven Failsafe for integration tests.
  • Document when to use unit tests, integration tests, contract tests, and SIT checks.
  • Apply the convention first to customer-service and account-service, then reuse it for future services.

Acceptance Criteria

  • ./mvnw test runs fast unit tests only.
  • ./mvnw verify runs unit tests and integration tests.
  • Integration tests use a clear naming convention such as *IT or *IntegrationTest.
  • CI output clearly separates unit test, integration test, and later quality-gate stages.
  • README or shared docs explain the testing model using practical examples.

Activity

  1. self-assigned this
    on Jun 30, 2026
  2. added theissue type on Jun 30, 2026
  3. ramioooz commented on Jul 3, 2026

    @ramioooz
    MemberAuthor

    Completed by applying the Surefire/Failsafe convention to customer-service and account-service, and documenting the shared CI/test-stage model in the .github repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions