也许有些人来到这里也很高兴将测试中的API作为服务运行。下面的CI Pipeline与Gitlab一起工作。但是，在运行器上调试它是丑陋的。就像这里已经建议的许多评论一样，我也更喜欢在staging环境中进行适当的端到端测试。它在某些情况下仍然很有用，调试也不太成问题，当你有shell访问runner上的作业时。

stages:
  - build
  - test

variables:
  IMAGE: $CI_REGISTRY_IMAGE

build_image:
  stage: build
  image:
    name: gcr.io/kaniko-project/executor:debug
    entrypoint: [""]
  script:
    - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
    - /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --destination $IMAGE:$CI_COMMIT_SHORT_SHA 
  tags:
   - k8s

test_image:
  stage: test
  services: 
    - name: docker.io/bitnami/postgresql:16
      alias: db
    - name: $IMAGE:$CI_COMMIT_SHORT_SHA  # api runs as service
      alias: my-api
  variables:
    POSTGRESQL_PASSWORD: $POSTGRESQL_PASSWORD
    POSTGRESQL_USER: $POSTGRESQL_USER
    POSTGRESQL_DATABASE: $POSTGRESQL_DATABASE
  image: alpine:latest # test script runs curl in alpine
  before_script:
    - apk add curl jq postgresql-client
  script:
    - "curl -s -X POST -H 'accept: application/json' 'my-api/items/?n=100&random=true'"
    - "curl -s -X GET  -H 'accept: application/json' 'my-api/items/' | jq '.[][].email'" 
    - "echo 'THIS test is a STUB, and the pipeline lacks health checks for services'"
  tags:
   - k8s

字符串