Test-More / Test-More/test-more

need better hints when modules are loaded in a weird order

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

Nobody has claimed this yet.

Dominant language
Perl
Stars
149
Forks
98
PR merge metrics
No merged PRs in 30d

Description

from #perl-qa:

14:00 < ether> > You should load Test::Tester before Test::Builder (or anything that loads Test::Builder) at /Volumes/chambord/Users/ether/perl5/perlbrew/perls/34.3/lib/5.34.3/Test/Tester.pm line 9.
14:00 < ether> it would help if that was a carp, not a warn; I have no idea what the culprit code is
14:00 < ether> Exodist: ^^
18:07 < Exodist> A carp is only half the battle. You will also need to know where tb was loaded. I am on my phone, not a laptop, can someone file a ticket? I also want to change that message to recommend 
                 more modern ways to test the test tools.
18:07 < ether> hmm good point, what matters is the first part, not when Test::Builder was loaded.
18:07 < ether> I'll file
18:08 < ether> I saw this when installing a bunch of distributions; I am not sure if it was from a particular dist's tests, or from cpanm itself, but presumably the former

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start at Test::Tester.pm line 9 and inspect the load-order diagnostic involving Test::Builder. No test file or command is named in the issue, so identify the relevant existing coverage before changing anything. Done means the diagnostic gives useful information about the culprit load location and reflects the requested testing guidance.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.