← Back to issue list

Add fetch-operator charmcraft tests

View original Github issue

Metadata

Project
fetch-service
Number
#203
Type
issue
State
closed
Author
cmatsuoka
Labels
—
Created
Updated
Closed

Current evaluation

Closed unimplemented with no resolving PR or commit; the sole comment created internal ticket CRAFT-3304, and fetch-operator Charmcraft tests were not added.

Resolution: closed stale

Reason: The issue record reports closure without a resolving PR or commit. Its only comment links internal ticket CRAFT-3304, and repository history showed no related implementation, indicating the work was abandoned.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done Use the proposed charmcraft test framework to add tests to fetch-operator. ### Why it needs to get done To verify charmcraft test ergonomics and functionality, and improve fetch-operator tests.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale Closed unimplemented with no resolving PR or commit; the sole comment created internal ticket CRAFT-3304, and fetch-operator Charmcraft tests were not added.
stealth/space-bunny-alpha — closed stale Closed unimplemented: no resolving PR or commit was found. The only comment created internal ticket CRAFT-3304; fetch-operator charmcraft tests were not added.
qwen/qwen3.6-35b-a3b — — Closed and abandoned. The charmcraft test addition for fetch-operator was not implemented, with tracking superseded by internal Jira ticket CRAFT-3304.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#225 Add GitHub workflow that builds and tests the fetch-operator charm fetch-service open Maintainer task (lengau) to add a CI workflow that builds the fetch-operator charm and runs `charmcraft test` with charmcraft.yaml pinned to the current fetch-service commit; still unimplemented.
73%
#2504 [WIP] Fix fetch-lib error in charmcraft 3.4.3 charmcraft closed Closed unmerged without tests, review, or CodeQL; the WIP fix was abandoned, while follow-up PR #2505 remains open for issue #2204.
71%