lpil / lpil/gleeunit

Can't find the project's tests if not run from the root

Open
#27 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Gleam
Stars
49
Forks
38
PR merge metrics
No merged PRs in 30d

Description

It looks like gleeunit is assuming to be run from the project's root. If we do the following it won't find any test:

gleam new foo
cd foo/test    # Or any other subdirectory
gleam test
# 0 tests run...

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

Reproduce the issue with gleam new foo, then run gleam test from foo/test and another subdirectory. Trace how gleeunit locates the project and its tests when the command is not run at the root. Done means the same tests are discovered and run from a project subdirectory.

Written by the indexing model from the issue text.

Assessment

Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.