test(install): coverage follow-ups from the #387 / #388 reviews
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start with check-uninstall.sh, check-install-safety.sh, tests/lib/install-home.sh, and check-install-manifest.sh; read each listed follow-up and the related review context from #387 and #388. Implement the test and helper changes in the checklist, then run all four installer checks under /bin/bash 3.2. Done means every box is checked and all four checks pass.
Written by the indexing model from the issue text.
Description
Test-only lows from the GLM reviews of the installer manifest (#387) and uninstall (#388) PRs. They were left under the review stop rule; none affects installer behaviour.
- check-uninstall.sh:
- Add a skip case where a link's text drifted from the recorded source.
- Add an uninstall run with managed settings present.
- Assert every skip carries a string
reason, so a skip can't slip through with onlyrestoreset. - Assert
managed_settings == []under the empty root. - Guard
$WORKinrun_at.
- check-install-safety.sh:
- Reap the lock-holder process when an assertion fails.
- Add a real two-install race on the flock, beyond the held-lock case.
- tests/lib/install-home.sh:
-
snap_tree's skip argument should prune a skipped directory's children. - Document that the lib owns the EXIT trap.
-
- check-install-manifest.sh:
- Field-check link records in plan mode, not only install mode.
Done when each box is checked and the four installer checks still pass under /bin/bash 3.2.
- Dominant language
- HTML
- Stars
- 347
- Forks
- 12
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 95
Getting set up
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 coco-research/coco
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coco-research/coco#539 ·
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coco-research/coco#538 ·
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
coco-research/coco#537 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coco-research/coco#530 ·
Maintainers usually reply within 1 day
-
check-asset-counts: bare 149 tripwire collides with a real active-assets count of 149Possibly taken @aryankalantri claimed this 1 day ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coco-research/coco#473 ·
Maintainers usually reply within 1 day
All issues in coco-research/coco
Similar issues
-
area: cli beginner beginner friendly bug community difficulty: easy dx easy first-timers-only good first issue hacktoberfest help wanted low-hanging fruit mentor available priority: P3 severity: low tech: typescript testing up-for-grabs ux
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
janitor-team/janitor#2590 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
karmada-io/karmada#8110 ·
Maintainers usually reply within 1 day