Check in mspec that no 2 specs have the same name

Open
#664 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
testing

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.

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.

Dominant language
Ruby
Stars
623
Forks
403
Avg merge
10h 38m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/spec

All issues in ruby/spec

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.