ASSERT-KTH / ASSERT-KTH/quixbugs-experiment
trace naming convention
Open
- Dominant language
- Java
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
`traces//trace__.json`
Example `traces/yajta/trace_BITCOUNT_test1.json`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking the repository's traces/ directory and comparing existing filenames with the convention shown in the issue. Clarify whether the convention should be documented or applied to files, then confirm that the intended trace paths follow the stated pattern.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100