Package QA Test Suite

Test Plan

As a follow up to #241028 (closed), this issue is to plan and track the implementation of a test suite for testing the GitLab package registry. See these comments for reference:

• #241028 (comment 402985597)
• #241028 (comment 408747777)
• #241028 (comment 408848075)

Introduction

To better guard against regressions and unintended affects of features (for example setting incorrect limits on file sizes), it is worthwhile to create a set of end to end feature tests for the package stage. This would include full workflows of working with the package APIs through their respective package manager clients.

Scope

• Maven
• NPM
• NuGet
• Conan
• PyPI
• Composer
• Generic package manager

Cases coverage matrix

Package Manager	Push action (upload)	Pull action (get pkgs from registry)	Search	Tags
Maven (mvn)	✅	gitlab-org/quality/testcases#1109 (closed)	n / a	n / a
Maven (gradle)	✅	gitlab-org/quality/testcases#1109 (closed)	n / a	n / a
NPM (npm)	✅	gitlab-org/quality/testcases#1110 (closed)	n / a
NuGet (nuget)	✅	gitlab-org/quality/testcases#1111 (closed)		n / a
NuGet (dotnet)	✅	gitlab-org/quality/testcases#1111 (closed)		n / a
Conan (conan)	✅	gitlab-org/quality/testcases#1112 (closed)		n / a
PyPI (pypi)	✅	gitlab-org/quality/testcases#1113 (closed)		n / a
Composer	✅	gitlab-org/quality/testcases#1114 (closed)	n / a	n / a
Generic	✅	✅	n / a	n / a