halo/e2e
Rick 2aac668df2
chore: upgrade the api-testing (e2e) to v0.0.16 (#5768)
* chore: upgrade the api-testing (e2e) to v0.0.16

* using the ghcr.io as the registry
2024-04-23 10:42:27 +08:00
..
Dockerfile chore: upgrade the api-testing (e2e) to v0.0.16 (#5768) 2024-04-23 10:42:27 +08: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 test: add e2e testing for the backend 2023-11-23 03:32:11 +00:00
testsuite.yaml feat: support reset passwords based on email address (#4941) 2023-12-01 03:06:09 +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