Check in mspec that no 2 specs have the same name
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 622
- Forks
- 402
- Avg merge
- 14h 51m
- Merged PRs (30d)
- 6
Description
Otherwise, tagging one spec actually skips both specs.
I think there are quite a few instances of this in ruby/spec, so we'll need renames in the specs before enforcing the check.
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 locating the mspec handling for spec names and scan the ruby/spec suite for duplicate names. Rename conflicting specs before enabling the duplicate-name check, then verify that tagging one spec no longer skips another.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100