No description
Find a file
Cristian Le 5beff4b8bc Add issue template (#1)
For now this has only one type of issue to request a new shared test

Co-authored-by: Cristian Le <git@lecris.dev>
Reviewed-on: #1
2026-06-17 10:11:36 +00:00
.fmf Initial commit 2026-02-10 17:45:17 +01:00
.forgejo/issue_template Add issue template (#1) 2026-06-17 10:11:36 +00:00
fedora-review Add fedora-review test 2026-04-01 13:46:48 +02:00
installability Initial commit 2026-02-10 17:45:17 +01:00
license-validate Add license-validate test 2026-04-29 13:49:25 +02:00
rmdepcheck Add rmdepcheck test 2026-04-01 13:45:40 +02:00
rpminspect Initial commit 2026-02-10 17:45:17 +01:00
rpmlint Initial commit 2026-02-10 17:45:17 +01:00
.env Initial commit 2026-02-10 17:45:17 +01:00
context.yaml Initial commit 2026-02-10 17:45:17 +01:00
CONTRIBUTING.md Initial commit 2026-02-10 17:45:17 +01:00
main.fmf Switch to main/stg branch workflow 2026-04-01 13:42:58 +02:00
README.md Initial commit 2026-02-10 17:45:17 +01:00

Fedora CI shared tests

TMT tests that are run on Fedora CI for each package.

This repo is composed of the references to the tmt plans that are being run. Navigate to the plans that are being imported for the actual implementations.

How to test locally

TMT tests are designed to be runnable locally with "minimal" input specifying what and how to test. These are passed via context and environment variables.

$ tmt -c @context.yaml run -e @.env plans --name /rpminspect

This command takes the context and environment variables from the files context.yaml and .env present in this repository. These files are only for reference, please edit them accordingly to point to the actual package you want to test. See the TMT Integration document for more details on the values that these variables should have. Each plan may have additional control parameters, see the actual plans implementations for more detail.