github
/
halo
mirror of https://github.com/halo-dev/halo
1
0
Fork 0
Code Issues Releases Wiki Activity
halo/e2e
History
Rick 7ca17001d9
chore: upgrade api-testing to v0.0.17 (#6253) 
<!--  Thanks for sending a pull request!  Here are some tips for you:
1. 如果这是你的第一次，请阅读我们的贡献指南：<https://github.com/halo-dev/halo/blob/main/CONTRIBUTING.md>。
1. If this is your first time, please read our contributor guidelines: <https://github.com/halo-dev/halo/blob/main/CONTRIBUTING.md>.
2. 请根据你解决问题的类型为 Pull Request 添加合适的标签。
2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request.
3. 请确保你已经添加并运行了适当的测试。
3. Ensure you have added or ran the appropriate tests for your PR.
-->

#### What type of PR is this?

<!--
添加其中一个类别：
Add one of the following kinds:

/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind improvement

适当添加其中一个或多个类别（可选）：
Optionally add one or more of the following kinds if applicable:

/kind api-change
/kind deprecation
/kind failing-test
/kind flake
/kind regression
-->

#### What this PR does / why we need it:

#### Which issue(s) this PR fixes:

<!--
PR 合并时自动关闭 issue。
Automatically closes linked issue when PR is merged.

用法：`Fixes #<issue 号>`，或者 `Fixes (粘贴 issue 完整链接)`
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
Fixes #

#### Special notes for your reviewer:

#### Does this PR introduce a user-facing change?

<!--
如果当前 Pull Request 的修改不会造成用户侧的任何变更，在 `release-note` 代码块儿中填写 `NONE`。
否则请填写用户侧能够理解的 Release Note。如果当前 Pull Request 包含破坏性更新（Break Change），
Release Note 需要以 `action required` 开头。
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
-->

```release-note
None
```
 		2024-07-02 15:21:24 +00:00
..
Dockerfile chore: upgrade api-testing to v0.0.17 (#6253) 2024-07-02 15:21:24 +00:00
Makefile test: run e2e testing on all supported databases 2023-11-29 05:39:51 +00:00
README.md test: add e2e test cases of user, role, and plugin (#4920) 2023-11-28 21:52:44 +08:00
compose-mysql.yaml test: run e2e testing on all supported databases 2023-11-29 05:39:51 +00:00
compose-postgres.yaml test: run e2e testing on all supported databases 2023-11-29 05:39:51 +00:00
compose.yaml test: run e2e testing on all supported databases 2023-11-29 05:39:51 +00:00
start.sh fix: the e2e script exit code handling is incorrect (#6097) 2024-07-02 11:07:23 +00:00
testsuite.yaml fix: the e2e script exit code handling is incorrect (#6097) 2024-07-02 11:07:23 +00:00

README.md

Please add the corresponding e2e (aka end-to-end) test cases if you add or update APIs.

How to work

  • Start and watch the docker-compose via the script
    • It has three containers: database, Halo, and testing
  • Run the e2e testing via api-testing
    • It will run the test cases from top to bottom
    • You can add the necessary asserts to it

Run locally

Please follow these steps if you want to run the e2e testing locally.

Please make sure you have installed docker-compose v2

  • Build project via ./gradlew clean build -x check in root directory of this repository
  • Build image via docker build . -t ghcr.io/halo-dev/halo-dev:main
  • Change the directory to e2e, then execute ./start.sh

Run Halo only

Please run the following command if you only want to run Halo.

docker-compose up halo