Running tests takes too long

Open
#429 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
perl
Domain
testing

Research direction

Start by measuring the full test run and identifying which integration tests account for the delay. Read the test organization and any release or smoker-test configuration to determine how tests are categorized. Done means normal end-user testing completes in a practical time while the broader tests remain available for release or smoker runs.

Written by the indexing model from the issue text.

Description

While updating Test2::Harness, I noticed it took a very long time to run all the tests.

It took me by surprise so I did not measure, but it ran for at least 15 minutes. From watching htop, it seemed like most of it was integration tests. My machine is not particularly slow, it's a T480 with i7.

Running this many tests on end machines is impractical, and may result in people installing the module with testing skipped, defeating the purpose. Please consider turning some tests into release-only or smoker-only tests.

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

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.

More from Test-More/Test2-Harness

All issues in Test-More/Test2-Harness

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.