How to Install and Uninstall python3-coverage-test-runner.noarch Package on Fedora 34

Last updated: February 11,2025

1. Install "python3-coverage-test-runner.noarch" package

This guide let you learn how to install python3-coverage-test-runner.noarch on Fedora 34


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                python3-coverage-test-runner.noarch
            
                    
    
    Copied

2. Uninstall "python3-coverage-test-runner.noarch" package

Learn how to uninstall python3-coverage-test-runner.noarch on Fedora 34:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                python3-coverage-test-runner.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the python3-coverage-test-runner.noarch package on Fedora 34

Last metadata expiration check: 2:32:10 ago on Tue Sep 6 14:10:38 2022.
Available Packages
Name : python3-coverage-test-runner
Version : 1.15
Release : 10.fc34
Architecture : noarch
Size : 33 k
Source : python-coverage-test-runner-1.15-10.fc34.src.rpm
Repository : fedora
Summary : Python module for enforcing code coverage completeness
URL : http://liw.fi/coverage-test-runner/
License : GPLv3+
Description : CoverageTestRunner is a Python module for running unit tests and
: failing them if the unit test module does not exercise all statements
: in the module it tests.
:
: For example, unit tests in module foo_tests.py are supposed to test
: everything in the foo.py module, and if they don't, it's a bug in the
: test coverage. It does not matter if other tests happen to test the
: missing parts. The unit tests for the module should test everything in
: that module.