How to Install and Uninstall python3-pytest-bdd.noarch Package on Fedora 39

Last updated: January 12,2025

1. Install "python3-pytest-bdd.noarch" package

Please follow the instructions below to install python3-pytest-bdd.noarch on Fedora 39


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                python3-pytest-bdd.noarch
            
                    
    
    Copied

2. Uninstall "python3-pytest-bdd.noarch" package

Please follow the steps below to uninstall python3-pytest-bdd.noarch on Fedora 39:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                python3-pytest-bdd.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the python3-pytest-bdd.noarch package on Fedora 39

Last metadata expiration check: 2:39:20 ago on Thu Mar 7 11:44:58 2024.
Available Packages
Name : python3-pytest-bdd
Version : 6.1.1
Release : 14.fc39
Architecture : noarch
Size : 97 k
Source : python-pytest-bdd-6.1.1-14.fc39.src.rpm
Repository : fedora
Summary : BDD library for the py.test runner
URL : https://pytest-bdd.readthedocs.io/en/latest/
License : MIT
Description : pytest-bdd implements a subset of the Gherkin language to enable automating
: project requirements testing and to facilitate behavioral driven development.
:
: Unlike many other BDD tools, it does not require a separate runner and benefits
: from the power and flexibility of pytest. It enables unifying unit and
: functional tests, reduces the burden of continuous integration server
: configuration and allows the reuse of test setups.
:
: Pytest fixtures written for unit tests can be reused for setup and actions
: mentioned in feature steps with dependency injection. This allows a true BDD
: just-enough specification of the requirements without maintaining any context
: object containing the side effects of Gherkin imperative declarations.