How to Install and Uninstall python39-stestr Package on openSuSE Tumbleweed

Last updated: December 29,2024

1. Install "python39-stestr" package

This guide let you learn how to install python39-stestr on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python39-stestr
            
                    
    
    Copied

2. Uninstall "python39-stestr" package

This is a short guide on how to uninstall python39-stestr on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python39-stestr
            
                    
    
    Copied

3. Information about the python39-stestr package on openSuSE Tumbleweed

Information for package python39-stestr:
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python39-stestr
Version : 4.1.0-2.4
Arch : noarch
Vendor : openSUSE
Installed Size : 667.0 KiB
Installed : No
Status : not installed
Source package : python-stestr-4.1.0-2.4.src
Upstream URL : https://github.com/mtreinish/stestr
Summary : A parallel Python test runner built around subunit
Description :
stestr is parallel Python test runner designed to execute unittest test suites
using multiple processes to split up execution of a test suite. It also will
store a history of all test runs to help in debugging failures and optimizing
the scheduler to improve speed. To accomplish this goal it uses the subunit
protocol to facilitate streaming and storing results from multiple workers.
stestr originally started as a fork of the testrepository project. But, instead
of being an interface for any test runner that used subunit, like testrepository,
stestr concentrated on being a dedicated test runner for python projects. While
stestr was originally forked from testrepository it is not backwards compatible
with testrepository. At a high level the basic concepts of operation are shared
between the two projects but the actual usage is not exactly the same.