mindspore-ai / mindspore-ai/hyper-parallel
用例整改，门禁耗时保障
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 63
- Avg merge
- 23h 45m
- Merged PRs (30d)
- 63
Description
背景
当前部分系统测试用例处于 level0 门禁范围，随着用例数量和执行复杂度增加，门禁耗时存在持续增长风险，需要进行长期治理。
目标
- 梳理 level0 / level1 用例分层，将非核心阻塞路径用例逐步下沉到 level1。
- 保障 level0 门禁聚焦核心冒烟能力，控制门禁整体耗时。
- 持续跟踪用例整改效果，减少门禁排队和执行时间波动。
范围
本 issue 作为长期治理入口，用于关联后续用例等级调整、门禁耗时优化和相关验证 PR。
schema_version: 1
source: gitcode
gitcode_repo: mindspore/hyper-parallel
gitcode_issue: 268
source_url: https://gitcode.com/mindspore/hyper-parallel/issues/268
Contributor guide
No contributing guide indexed for this repository
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 inventorying the repository's level0 and level1 test cases and reviewing available gate execution-time data. Define which non-core blocking-path cases can move to level1, then validate that level0 remains focused on core smoke coverage and that gate duration and queue variability improve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100