What did the pipeline for running automated tests look like?

A typical pipeline for running automated tests includes the following stages:

1. Build the project — compile and prepare artifacts.
2. Run unit tests — quick tests at the module level.
3. Run integration tests — verify component interactions.
4. Run UI/end-to-end tests — automate user scenarios.
5. Analyze results — collect logs, reports, coverage metrics.
6. Notifications — send results to the team (e.g., Slack or email).

The pipeline is usually automated using CI/CD systems (Jenkins, GitLab CI, GitHub Actions). Example configuration for GitLab CI:

stages:
  - build
  - test

build_job:
  stage: build
  script:
    - ./gradlew build

test_unit:
  stage: test
  script:
    - ./gradlew test

test_integration:
  stage: test
  script:
    - ./gradlew integrationTest

report:
  stage: test
  script:
    - ./gradlew jacocoTestReport
  artifacts:
    paths:
      - build/reports/