运行 python Azure 管道中的单元测试不会失败，即使它应该失败
Running python unittests in azure pipeline doesn't fail even though it should
我想 运行 在我的 docker-compose 应用程序中进行单元测试，作为 Azure DevOps 管道的一部分。问题是测试在本地失败，但当我在管道中 运行 它们时它们不会失败。这些是我的代码的相关部分：
docker-compose 配置设置了一个 python 应用程序和一个 MySQL 图像。单元测试 运行ning 针对应用服务中的数据库服务：
services:
app:
build: .
ports:
- '8080:8080'
command: ./make.sh unittests_entrypoint
stdin_open: false # docker run -i
tty: false # docker run -t
depends_on:
- db
environment:
- DB_USER_TEST
- DB_PASSWORD_TEST
- DB_HOST_TEST
- DB_NAME_TEST
db:
image: mysql:8.0.29
tty: false # docker run -t
stdin_open: false
ports:
- '8000:8000'
environment:
- MYSQL_ROOT_PASSWORD
- MYSQL_DATABASE
- DB_USER_TEST
- DB_PASSWORD_TEST
- DB_HOST_TEST
- DB_NAME_TEST
当 运行ning docker-compose up -d --build 应用程序服务启动 unittests_entrypoint 等待数据库启动，然后 运行 对 dbservice 进行单元测试：
# Inside make.sh
unittests_entrypoint () {
echo "Waiting for database boot process to finish..."
sleep 30
python -m unittest # Run unittests
}
当 运行 在本地进行此操作时，测试失败，这正是我此时所期望的：
app_1 | .F...
app_1 | ======================================================================
app_1 | FAIL: test_status_get (test.test_app.MyTest)
app_1 | Tests the status code of successful GET on route '/api/v1/book'.
app_1 | ----------------------------------------------------------------------
app_1 | Traceback (most recent call last):
app_1 | File "/app/test/test_app.py", line 32, in test_status_get
app_1 | self.assertEqual(response.status_code, 404)
app_1 | AssertionError: 200 != 404
app_1 |
app_1 | ----------------------------------------------------------------------
app_1 | Ran 5 tests in 2.410s
app_1 |
app_1 | FAILED (failures=1)
但是，当我 运行 在我的天蓝色管道中执行此操作时，它不会失败。我管道的相关部分如下所示：
- task: Bash@3
inputs:
targetType: 'inline'
script: 'docker-compose up -d --build'
env:
DB_HOST_TEST: $(DB_HOST_TEST_ENV)
DB_USER_TEST: $(DB_USER_TEST_ENV)
DB_PASSWORD_TEST: $(DB_PASSWORD_TEST_ENV)
DB_NAME_TEST: $(DB_NAME_TEST_ENV)
MYSQL_ROOT_PASSWORD: $(MYSQL_ROOT_PASSWORD_ENV)
MYSQL_DATABASE: $(MYSQL_DATABASE_ENV)
天蓝色管道中我的 docker-compose 任务的输出结束（在此之后它只是继续下一个管道阶段，但它实际上应该停止执行管道，因为测试失败）：
Removing intermediate container 4cd86b544f4f
---> 800f62d5bf2d
Step 5/8 : COPY . .
---> 8a951e53d1a3
Step 6/8 : RUN chmod +x src/app.py src/***.py test/test_app.py
---> Running in 6fb14e7391b6
Removing intermediate container 6fb14e7391b6
---> 9d4ca1466dd2
Step 7/8 : EXPOSE 8080
---> Running in b994322b776e
Removing intermediate container b994322b776e
---> 840f747945ae
Step 8/8 : CMD ["./src/app.py"]
---> Running in 36552f8c4a73
Removing intermediate container 36552f8c4a73
---> 281f6467578c
Successfully built 281f6467578c
Successfully tagged s_app:latest
Creating s_***_1 ...
Creating s_***_1 ... done
Creating s_app_1 ...
Creating s_app_1 ... done
Finishing: Bash
如您所见，测试不会像在本地那样失败，尽管它们应该失败。我做错了什么？
编辑：
运行 仅 docker-compose up --build 给出了一个奇怪的输出，其中 0 测试 运行 并且数据库抱怨“localhost 是使用空密码创建的”，而当我 运行 它在本地。此外，管道无法继续，因为数据库容器保持 运行ning。身份验证所需的所有环境变量均已正确设置。
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1debian10 started.
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1debian10 started.
***_1 | 2022-05-10T16:56:44.256776Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.29) initializing of server in progress as process 43
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Initializing database files
***_1 | 2022-05-10T16:56:44.261370Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
***_1 | 2022-05-10T16:56:44.618226Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
app_1 | Waiting for database boot process to finish...
***_1 | 2022-05-10T16:56:45.346210Z 6 [Warning] [MY-010453] [Server] ***@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
***_1 | 2022-05-10 16:56:47+00:00 [Note] [Entrypoint]: Database files initialized
***_1 | 2022-05-10 16:56:47+00:00 [Note] [Entrypoint]: Starting temporary server
***_1 | 2022-05-10T16:56:47.675567Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 90
***_1 | 2022-05-10T16:56:47.688327Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
***_1 | 2022-05-10T16:56:47.838394Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
***_1 | 2022-05-10T16:56:48.007316Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
***_1 | 2022-05-10T16:56:48.007356Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
***_1 | 2022-05-10T16:56:48.010147Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
***_1 | 2022-05-10T16:56:48.026597Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: /var/run/mysqld/mysqlx.sock
***_1 | 2022-05-10T16:56:48.027127Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.29' socket: '/var/run/mysqld/mysqld.sock' port: 0 MySQL Community Server - GPL.
app_1 |
app_1 | ----------------------------------------------------------------------
app_1 | Ran 0 tests in 0.000s
app_1 |
app_1 | OK
s_app_1 exited with code 0
##[error]The operation was canceled.
Finishing: Bash
您需要启动分离的数据库，然后 运行 您的应用程序作为一次性命令，并确保它 returns 在失败的测试中使用 non-zero 退出代码：
steps:
- script: |
docker compose run --use-aliases --detach mysql
docker compose run app
- script: docker compose down --volumes
condition: always()
我正在 运行ning composed down with the always condition to clean up，即使测试失败了。
或者，您可以将容器资源用作 sidecar 服务。这可能看起来像这样：
resources:
containers:
- container: mysql
image: mysql:8.0.29
ports:
- 127.0.0.1:3306:3306
environment:
- MYSQL_ROOT_PASSWORD=test
- MYSQL_DATABASE=test
- DB_USER_TEST=test
- DB_PASSWORD_TEST=test
- DB_HOST_TEST=test
- DB_NAME_TEST=test
services:
mysql: mysql
steps:
- script: docker build -t app .
- script: |
docker run --network host \
-e DB_HOST_TEST=127.0.0.1 \
-e DB_USER_TEST=test \
-e DB_PASSWORD_TEST=test \
-e DB_NAME_TEST=test \
app ./make.sh unittests_entrypoint
这样做会为您清理干净。
我想 运行 在我的 docker-compose 应用程序中进行单元测试，作为 Azure DevOps 管道的一部分。问题是测试在本地失败，但当我在管道中 运行 它们时它们不会失败。这些是我的代码的相关部分：
docker-compose 配置设置了一个 python 应用程序和一个 MySQL 图像。单元测试 运行ning 针对应用服务中的数据库服务：
services:
app:
build: .
ports:
- '8080:8080'
command: ./make.sh unittests_entrypoint
stdin_open: false # docker run -i
tty: false # docker run -t
depends_on:
- db
environment:
- DB_USER_TEST
- DB_PASSWORD_TEST
- DB_HOST_TEST
- DB_NAME_TEST
db:
image: mysql:8.0.29
tty: false # docker run -t
stdin_open: false
ports:
- '8000:8000'
environment:
- MYSQL_ROOT_PASSWORD
- MYSQL_DATABASE
- DB_USER_TEST
- DB_PASSWORD_TEST
- DB_HOST_TEST
- DB_NAME_TEST
当 运行ning docker-compose up -d --build 应用程序服务启动 unittests_entrypoint 等待数据库启动，然后 运行 对 dbservice 进行单元测试：
# Inside make.sh
unittests_entrypoint () {
echo "Waiting for database boot process to finish..."
sleep 30
python -m unittest # Run unittests
}
当 运行 在本地进行此操作时，测试失败，这正是我此时所期望的：
app_1 | .F...
app_1 | ======================================================================
app_1 | FAIL: test_status_get (test.test_app.MyTest)
app_1 | Tests the status code of successful GET on route '/api/v1/book'.
app_1 | ----------------------------------------------------------------------
app_1 | Traceback (most recent call last):
app_1 | File "/app/test/test_app.py", line 32, in test_status_get
app_1 | self.assertEqual(response.status_code, 404)
app_1 | AssertionError: 200 != 404
app_1 |
app_1 | ----------------------------------------------------------------------
app_1 | Ran 5 tests in 2.410s
app_1 |
app_1 | FAILED (failures=1)
但是，当我 运行 在我的天蓝色管道中执行此操作时，它不会失败。我管道的相关部分如下所示：
- task: Bash@3
inputs:
targetType: 'inline'
script: 'docker-compose up -d --build'
env:
DB_HOST_TEST: $(DB_HOST_TEST_ENV)
DB_USER_TEST: $(DB_USER_TEST_ENV)
DB_PASSWORD_TEST: $(DB_PASSWORD_TEST_ENV)
DB_NAME_TEST: $(DB_NAME_TEST_ENV)
MYSQL_ROOT_PASSWORD: $(MYSQL_ROOT_PASSWORD_ENV)
MYSQL_DATABASE: $(MYSQL_DATABASE_ENV)
天蓝色管道中我的 docker-compose 任务的输出结束（在此之后它只是继续下一个管道阶段，但它实际上应该停止执行管道，因为测试失败）：
Removing intermediate container 4cd86b544f4f
---> 800f62d5bf2d
Step 5/8 : COPY . .
---> 8a951e53d1a3
Step 6/8 : RUN chmod +x src/app.py src/***.py test/test_app.py
---> Running in 6fb14e7391b6
Removing intermediate container 6fb14e7391b6
---> 9d4ca1466dd2
Step 7/8 : EXPOSE 8080
---> Running in b994322b776e
Removing intermediate container b994322b776e
---> 840f747945ae
Step 8/8 : CMD ["./src/app.py"]
---> Running in 36552f8c4a73
Removing intermediate container 36552f8c4a73
---> 281f6467578c
Successfully built 281f6467578c
Successfully tagged s_app:latest
Creating s_***_1 ...
Creating s_***_1 ... done
Creating s_app_1 ...
Creating s_app_1 ... done
Finishing: Bash
如您所见，测试不会像在本地那样失败，尽管它们应该失败。我做错了什么？
编辑：
运行 仅 docker-compose up --build 给出了一个奇怪的输出，其中 0 测试 运行 并且数据库抱怨“localhost 是使用空密码创建的”，而当我 运行 它在本地。此外，管道无法继续，因为数据库容器保持 运行ning。身份验证所需的所有环境变量均已正确设置。
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1debian10 started.
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.29-1debian10 started.
***_1 | 2022-05-10T16:56:44.256776Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.29) initializing of server in progress as process 43
***_1 | 2022-05-10 16:56:44+00:00 [Note] [Entrypoint]: Initializing database files
***_1 | 2022-05-10T16:56:44.261370Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
***_1 | 2022-05-10T16:56:44.618226Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
app_1 | Waiting for database boot process to finish...
***_1 | 2022-05-10T16:56:45.346210Z 6 [Warning] [MY-010453] [Server] ***@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
***_1 | 2022-05-10 16:56:47+00:00 [Note] [Entrypoint]: Database files initialized
***_1 | 2022-05-10 16:56:47+00:00 [Note] [Entrypoint]: Starting temporary server
***_1 | 2022-05-10T16:56:47.675567Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 90
***_1 | 2022-05-10T16:56:47.688327Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
***_1 | 2022-05-10T16:56:47.838394Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
***_1 | 2022-05-10T16:56:48.007316Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
***_1 | 2022-05-10T16:56:48.007356Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
***_1 | 2022-05-10T16:56:48.010147Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
***_1 | 2022-05-10T16:56:48.026597Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: /var/run/mysqld/mysqlx.sock
***_1 | 2022-05-10T16:56:48.027127Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.29' socket: '/var/run/mysqld/mysqld.sock' port: 0 MySQL Community Server - GPL.
app_1 |
app_1 | ----------------------------------------------------------------------
app_1 | Ran 0 tests in 0.000s
app_1 |
app_1 | OK
s_app_1 exited with code 0
##[error]The operation was canceled.
Finishing: Bash
您需要启动分离的数据库，然后 运行 您的应用程序作为一次性命令，并确保它 returns 在失败的测试中使用 non-zero 退出代码：
steps:
- script: |
docker compose run --use-aliases --detach mysql
docker compose run app
- script: docker compose down --volumes
condition: always()
我正在 运行ning composed down with the always condition to clean up，即使测试失败了。
或者，您可以将容器资源用作 sidecar 服务。这可能看起来像这样：
resources:
containers:
- container: mysql
image: mysql:8.0.29
ports:
- 127.0.0.1:3306:3306
environment:
- MYSQL_ROOT_PASSWORD=test
- MYSQL_DATABASE=test
- DB_USER_TEST=test
- DB_PASSWORD_TEST=test
- DB_HOST_TEST=test
- DB_NAME_TEST=test
services:
mysql: mysql
steps:
- script: docker build -t app .
- script: |
docker run --network host \
-e DB_HOST_TEST=127.0.0.1 \
-e DB_USER_TEST=test \
-e DB_PASSWORD_TEST=test \
-e DB_NAME_TEST=test \
app ./make.sh unittests_entrypoint
这样做会为您清理干净。