Comment 2 for bug 1915507

Hi Robie, I don't think the situation has changed in terms of snapcraft or LP features around snap package pre-upload testing; may I suggest one of the following strategies to unblock this:

1) uploading but not releasing/publishing new snap builds to the edge channel until they are tested (need to run the test outside of Launchpad, snap download --revision should work if logged in)

2) uploading and releasing to edge channel, testing immediately afterwards, rolling back the edge channel to previous published in case of regressions (this window would be short, and it's edge after all)

3) testing of the prime/ directory triggered as a post-build step of the last snapcraft part

4) upload of the snap from your CI/CD instead of the one from Launchpad

5) upload to a branch of edge (channel), run the tests outside of Launchpad, then promote to edge

I haven't tested these options, and I don't see the current non-LP CI/CD (in Travis IIUC?), so not sure how easy it is, but 5) might be relatively short to implement; perhaps 3) is also relatively straightforward and requires less CI/CD config changes.