How to Install and Uninstall python-pytest-bdd-doc.noarch Package on Fedora 35

Last updated: July 01,2024

1. Install "python-pytest-bdd-doc.noarch" package

Please follow the guidelines below to install python-pytest-bdd-doc.noarch on Fedora 35


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                python-pytest-bdd-doc.noarch
            
                    
    
    Copied

2. Uninstall "python-pytest-bdd-doc.noarch" package

This guide covers the steps necessary to uninstall python-pytest-bdd-doc.noarch on Fedora 35:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                python-pytest-bdd-doc.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the python-pytest-bdd-doc.noarch package on Fedora 35

Last metadata expiration check: 1:27:34 ago on Wed Sep 7 02:25:42 2022.
Available Packages
Name : python-pytest-bdd-doc
Version : 4.1.0
Release : 6.fc35
Architecture : noarch
Size : 179 k
Source : python-pytest-bdd-4.1.0-6.fc35.src.rpm
Repository : updates
Summary : Documentation for pytest-bdd
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.