← Back to issue list

snapcraft-parser has no integration tests

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1590268
Type
issue
State
closed
Author
~elopio
Labels
verification-done
Created
Updated
Closed

Current evaluation

Added a user-level happy-path integration test for snapcraft-parser via merged canonical/snapcraft#560 (commit 8f5b30dba); released in Snapcraft 2.12.

Resolution: closed resolved

Reason: canonical/snapcraft#560 merged commit 8f5b30dba, adding an integration test that invokes snapcraft-parser as a user. The resulting 2.12 package completed SRU verification and was released to xenial-updates.

Evaluated by: mr-cal-bot

No scores available.

Issue body

The snapcraft-parser needs tests that call the binary as a user would do it. [Impact] * Without an integration test, all the units of code might be working but the executable might not. * This will let us do future changes to the parser with more confidence. [Test Case] * Run the snapcraft parser test of the integration suite. [Regression Potential] * This could make the integration suite to start failing. It is part of the autopkgtest, so that would block the release. We are covered.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Added a user-level happy-path integration test for snapcraft-parser via merged canonical/snapcraft#560 (commit 8f5b30dba); released in Snapcraft 2.12.
stealth/space-bunny-alpha — closed resolved Added a happy-path integration test that invokes snapcraft-parser as a user; merged in canonical/snapcraft#560 via commit 8f5b30dba.
stealth/space-bunny-alpha — closed resolved Added a snapcraft-parser integration test that invokes the binary; PR canonical/snapcraft#560 was merged in commit 8f5b30dba.
qwen/qwen3.6-35b-a3b — — Integration tests for snapcraft-parser were implemented and verified, resolving the issue. The added tests validate the binary as a user would run it, ensuring executable reliability and safe future changes within the autopkgtest suite.
qwen/qwen3.6-35b-a3b — — Resolved by adding integration tests for snapcraft-parser to verify end-to-end execution and support future changes. The request was fulfilled and closed with verification completed.
qwen/qwen3.6-35b-a3b — — Integration tests for snapcraft-parser were implemented and verified, resolving the lack of user-level binary validation. The request was fulfilled and the issue closed.

Update history

Date Change
created

Related work

  • Likely Fixed By: canonical/snapcraft#560 (confidence 100%)

    Merged PR adding the snapcraft-parser happy-path integration test in commit 8f5b30dba.

Related issues

Issue Project State Summary Similarity
#560 Add snapcraft-parser integration test. snapcraft merged Merged PR #560 added the snapcraft-parser happy-path integration test in commit 8f5b30dba.
88%
#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.
74%
#202 Add snapcraft tests fetch-service open Snap package integration tests were added and CI now runs the Spread suite through snapcraft test, although the tracking issue remains open.
72%
#1752580 tests.integration.general.test_parser.TestParserWikis fails snapcraft (launchpad) closed Integration test failed due to missing snapcraft-parser binary; closed as stale by maintainer.
72%
#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).
72%