There are no tests for the 'domain' command
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the test-harness and the implementation or existing tests for the domain command, then review how other command test scripts set up basic calls. Add coverage for several basic domain calls and their setup, and run the relevant test script to confirm the missing cases are covered.
Written by the indexing model from the issue text.
Description
Let's get a test-script with at least a few basic calls/setup for domains into the test-harness. We could have caught #769 way earlier if we'd had them.
- Dominant language
- Python
- Stars
- 43
- Forks
- 52
- Avg merge
- 11h 38m
- Merged PRs (30d)
- 11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pulp/pulp-cli
-
bug Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
easy fix feature request
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
bug Triage-Needed
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
use-agent-os/agent-os#3314 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AiursoftWeb/AnduinOS-2#19 ·