Do not use absolute paths in test fixtures

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

Start with the files changed in pull request 144 and inspect the text fixtures that contain absolute paths. Trace how those fixtures are loaded by the tests, then confirm that the tests work without machine-specific paths and that the full relevant test set passes.

Written by the indexing model from the issue text.

Description

In cases like, we should not have to update the paths to all the test files https://github.com/nexB/python-inspector/pull/144/files#diff-51ccb793e30e705b5cabbdac167f507a4aa2398f1edc47cab891417ca7164ed5L7

Instead we should not use absolute paths in text fixtures

Dominant language
Python
Stars
23
Forks
29
Avg merge
1h 7m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 aboutcode-org/python-inspector

All issues in aboutcode-org/python-inspector

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.