← Back to issue list

Add snapcraft tests

View original Github issue

Metadata

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

Current evaluation

Snap package integration tests were added and CI now runs the Spread suite through snapcraft test, although the tracking issue remains open.

Suggested action: close resolved

Reason: Commit 323b0e1 (fetch-service#386), “tests: update testing to use craft-test,” completed the test-framework migration after 8fe0091 added initial Spread coverage. The current workflow explicitly runs “snapcraft test --verbose,” and spread.yaml defines three snap integration suites, so the requested work is present despite the issue remaining open.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 14 Complexity: 55 Confidence: 96 Actionability: 68

Issue body

### What needs to get done Use the proposed snapcraft test framework and create tests for the fetch service snap package. ### Why it needs to get done To check the ergonomics and functional aspects of snapcraft test, and improve fetch-service tests.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 14
Complexity: 55
Confidence: 96
Actionability: 68
close resolved Snap package integration tests were added and CI now runs the Spread suite through snapcraft test, although the tracking issue remains open.
stealth/space-bunny-alpha
Impact: 42
Quick Win: 10
Complexity: 50
Confidence: 73
Actionability: 48
needs triage Fetch-service snap package still needs integration tests using Snapcraft’s proposed test framework; the scope and target coverage remain unspecified and awaiting maintainer triage.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 30
Staleness: 85
Complexity: 25
Confidence: 65
Support Request: 15
close stale Feature request to add snapcraft tests for the fetch service snap package using the proposed test framework. Issue is 744 days old with no maintainer engagement beyond an auto-generated Jira sync.

Update history

Date Change
created

Related work

  • Likely Fixed By: fetch-service#386 (confidence 97%)

    The commit migrated the test infrastructure to craft-test, matching the requested Snapcraft test framework.

  • Likely Fixed By: fetch-service#269 (confidence 92%)

    This commit added the initial Spread integration suite that the current Snapcraft test job executes.

Related issues

Issue Project State Summary Similarity
#1272 tests: initial setup for the snapcraft snap tests with spread snapcraft merged Merged PR #1272 as commit 545344442, adding initial Spread-based test infrastructure for the snapcraft snap.
79%
#706 Add integration tests using the snap charmcraft closed Snap-based integration coverage was added through Charmcraft's Spread suite by merged PR canonical/charmcraft#862 (commit 7790c044).
77%
#1038 ci(spread): switch from manually running spread to using snapcraft test craft-application open Migrates dogfooding Spread runs to snapcraft test; after 197 days it remains unreviewed with seven CI failures, including all craft-test jobs and snap-tests.
76%
#386 tests: update testing to use craft-test fetch-service merged Merged #386 as commit 323b0e1, replacing direct Spread calls with snapcraft test and updating the test base to core24.
75%
#5845 test(spread): test building base and snapd snaps snapcraft merged Merged as fb8c81e8f, adding manual Spread coverage that builds current base snaps and the snapd snap against mainline Snapcraft.
75%
#2212 tests: add spread suite for ruby plugin snapcraft merged Merged PR snapcore/snapcraft#2212 (commit b7729970a) adds a Spread suite for the Ruby plugin, replacing the Python/snapd integration test; closes LP #1783840.
74%
#50 test: test the snapcraft actions craft-actions merged Merged PR #50 added Snapcraft action tests adapted from Charmcraft’s suite, with all reported CI checks passing.
73%
#806 Use `snapcraft test` for spread tests craft-application open Maintainer dogfooding task: switch CI from invoking spread directly to `snapcraft test`. Triaged but unimplemented — .github/workflows/spread.yaml still calls `spread ${{ matrix.spread }}`; open PR #1038 attempts it with failing CI.
73%
#2203 tests: add spread suite for kbuild plugin snapcraft merged Merged into snapcraft master as 67d94bd4 (squashed commit f5d1b1741), adding tests/spread/plugins/kbuild and moving Kbuild plugin integration tests out of the Python unit suite; closes LP bug #1783835.
73%
#1625 tests: use the snapcraft snap for integration tests snapcraft merged Merged PR #1625 updated integration tests to run the installed Snapcraft snap, better matching the user environment. Resolution: commit eebb070e6.
73%