How to Install and Uninstall python310-testrepository Package on openSuSE Tumbleweed
Last updated: November 23,2024
1. Install "python310-testrepository" package
This tutorial shows how to install python310-testrepository on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python310-testrepository
Copied
2. Uninstall "python310-testrepository" package
Please follow the step by step instructions below to uninstall python310-testrepository on openSuSE Tumbleweed:
$
sudo zypper remove
python310-testrepository
Copied
3. Information about the python310-testrepository package on openSuSE Tumbleweed
Information for package python310-testrepository:
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-testrepository
Version : 0.0.20-10.4
Arch : noarch
Vendor : openSUSE
Installed Size : 669.3 KiB
Installed : No
Status : not installed
Source package : python-testrepository-0.0.20-10.4.src
Upstream URL : https://github.com/testing-cabal/testrepository
Summary : A repository of test results
Description :
This project provides a database of test results which can be used as part of
developer workflow to ensure/check things like:
* No commits without having had a test failure, test fixed cycle.
* No commits without new tests being added.
* What tests have failed since the last commit (to run just a subset).
* What tests are currently failing and need work.
Test results are inserted using subunit (and thus anything that can output
subunit or be converted into a subunit stream can be accepted).
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-testrepository
Version : 0.0.20-10.4
Arch : noarch
Vendor : openSUSE
Installed Size : 669.3 KiB
Installed : No
Status : not installed
Source package : python-testrepository-0.0.20-10.4.src
Upstream URL : https://github.com/testing-cabal/testrepository
Summary : A repository of test results
Description :
This project provides a database of test results which can be used as part of
developer workflow to ensure/check things like:
* No commits without having had a test failure, test fixed cycle.
* No commits without new tests being added.
* What tests have failed since the last commit (to run just a subset).
* What tests are currently failing and need work.
Test results are inserted using subunit (and thus anything that can output
subunit or be converted into a subunit stream can be accepted).