E2E test guide
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
Add developer about how to run E2E test guide in local dev environment.
About how to write the doc, you can refer UT's user guide: https://github.com/kmesh-net/website/pull/41
And the E2E test framework design can refer here: https://github.com/kmesh-net/kmesh/blob/main/docs/proposal/e2e.md
You can try to try running the tests locally yourself, extracting some of the content in the proposal, such as the use of the command line flags, and extending it appropriately. So as to wirte a doc that can make it easy for other developers to get started.
@noobwei
Contributor guide
Research direction
Start with the E2E framework design in docs/proposal/e2e.md and use website PR #41 as the guide's documentation model. Run the E2E tests locally to verify setup and command-line flags, then document the local developer workflow and how to get started successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100