pingcap / pingcap/tidb-operator
e2e: stability tests migration
Open
Nobody has claimed this yet.
lifecycle/frozen
status/help-wanted
test/e2e
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Describe the feature you'd like:
Migrate current stability tests into the e2e framework.
Part of https://docs.google.com/document/d/1-GHQ9zWNjTjTt-CxwhNEnOku8D58qLzQLT6WX_CeeUI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked design document and locating the current stability tests in the repository. Identify the e2e framework's expected structure, then migrate the existing stability tests into it. Done means the current stability coverage is represented and runnable through the e2e framework.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100