docs: Add back end E2E test document

[Jaycean]

Please answer these questions before submitting a pull request

• Why submit this pull request?

• Bugfix

• New feature provided

• Improve performance

• Backport patches

• Related issues
  fix Doc: Add the document of backend E2E environment #1380

---

New feature or improvement

• Add back-end E2E test environment construction and test steps

[codecov-io]

Codecov Report

Merging #1381 (36ec862) into master (9cb9aa7) will increase coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1381      +/-   ##
==========================================
+ Coverage   65.42%   65.56%   +0.14%     
==========================================
  Files          43       44       +1     
  Lines        2655     2933     +278     
==========================================
+ Hits         1737     1923     +186     
- Misses        713      778      +65     
- Partials      205      232      +27     

Impacted Files	Coverage Δ
api/internal/utils/utils.go	67.07% <0.00%> (-4.14%)	⬇️
api/internal/core/storage/etcd.go	44.44% <0.00%> (-4.05%)	⬇️
api/internal/conf/conf.go	67.85% <0.00%> (ø)
api/internal/utils/closer.go	33.33% <0.00%> (ø)
api/internal/filter/schema.go	55.46% <0.00%> (ø)
api/internal/handler/data_loader/route_import.go	64.91% <0.00%> (ø)
api/internal/core/store/validate.go	69.27% <0.00%> (+0.34%)	⬆️
api/internal/handler/data_loader/route_export.go	69.17% <0.00%> (+0.47%)	⬆️
api/internal/route.go	84.84% <0.00%> (+0.47%)	⬆️
api/internal/core/store/store.go	86.66% <0.00%> (+0.59%)	⬆️
... and 2 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9cb9aa7...36ec862. Read the comment docs.

[liuxiran]

LGTM from the style

[Jaycean]

At present, the document only provides a separate use of docker to start upstream node. Manage-API, and admin-API to start using source code. I plan to update the document of using docker-compose to start E2E cluster.

[Jaycean]

At present, using the source code to start this method needs to modify the E2E test IP, the implementation method is not very friendly, do you have better suggestions？
cc @nic-chen @starsz @imjoey

[imjoey]

@Jaycean Since within this step, developers are required to change every single occurrence for IP address of upstream nodes. Cause I believe that we need to cover all test cases even for only few changes. So I'm afraid this is not a rather practical way. How about just guide developers to setup docker-compose environment for local e2e testing? Thanks.

[nic-chen]

I use docker-compose to run local e2e testing. when I update the main code, just delete the image of Manager API and let it rebuild. building the image of Manager API only takes a little time.

[imjoey]

I use docker-compose to run local e2e testing. when I update the main code, just delete the image of Manager API and let it rebuild. building the image of Manager API only takes a little time.

@nic-chen yep, from my perspective, yours is much better and even easier. Thanks for sharing.

[Jaycean]

I updated the steps of using docker compose for E2E testing. It's really unfriendly to start the method locally according to the source code, so is this method left for developers to choose, or is it just run with docker compose?

[starsz]

Good. Using docker-compose for E2E is a better way.

[imjoey]

@Jaycean current doc is awesome. Thanks for the update.

[starsz]

@juzhiyuan @LiteSun Please take a look at the FE test.

[LiteSun]

@juzhiyuan @LiteSun Please take a look at the FE test.

ok.

ping @guoqqqi https://github.com/apache/apisix-dashboard/pull/1381/checks?check_run_id=1788500888

[imjoey]

/lgtm
Thanks @Jaycean . We can merge this once CI passes.