Restore nameko tests

Open
#609 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
38/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
build-system, testing

Research direction

Start by reviewing the tox configuration changed in #608 and the existing Nameko test setup. Restore the Nameko tests in their own tox environment, then run that environment and the other integration environments to verify the version conflict is isolated.

Written by the indexing model from the issue text.

Description

Disabled in #608. Due to its kombu version conflict with Celery, nameko will need testing in its own tox environment. To be fair, the tox environments could be split by integration anyway, to prevent such conflicts.

Dominant language
Python
Stars
77
Forks
19
Avg merge
1d 9h
Merged PRs (30d)
5

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 scoutapp/scout_apm_python

All issues in scoutapp/scout_apm_python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.