fix: reorganize workspace directories — move plans/reports out of 执行日志#175
Merged
Conversation
added 3 commits
June 2, 2026 03:28
…-version breakage
Two bugs fixed:
1. ThreadGroup <intProp>/<longProp> containing ${THREADS}/${RAMPUP}/${DURATION}
→ changed to <stringProp> (JMeter runtime eval, not XML parse time)
2. Removed hardcoded <objProp name="saveConfig"> from ResultCollector
→ delegates to jmeter.properties defaults, compatible with JMeter 5.0~5.6.3
Added version compatibility banner documenting both constraints.
- Move 7 JSON files (plans/checklists/summaries) from 执行日志 to 测试计划/需求分析/测试报告 - Move decisions/ from 执行日志 to 测试报告 (AI decision records, not execution logs) - Move allure-results/ from 执行日志 to 测试报告 (report raw data, not execution logs) - Update 24 files with path references to match new locations (zero residual old paths)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
执行日志/to correct directories (测试计划/需求分析/测试报告)decisions/from执行日志/to测试报告/(AI decision records belong to report system)allure-results/from执行日志/to测试报告/(report raw data, not execution logs)Changes
Why
执行日志/should only contain execution artifacts (logs, screenshots, JTL, traces). Plans, summaries, decision records, and report data belong in their respective stage directories. This makes the workspace structure self-documenting and follows the principle of organizing by artifact type.Test plan
执行日志/decisionsreferences in codebase执行日志/allure-resultsreferences in codebase执行日志/bug_drafts.jsonetc. references in codebase