How to Install and Uninstall python39-pytest-bdd Package on openSuSE Tumbleweed

Last updated: November 23,2024

1. Install "python39-pytest-bdd" package

Please follow the guidelines below to install python39-pytest-bdd on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python39-pytest-bdd
            
                    
    
    Copied

2. Uninstall "python39-pytest-bdd" package

In this section, we are going to explain the necessary steps to uninstall python39-pytest-bdd on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python39-pytest-bdd
            
                    
    
    Copied

3. Information about the python39-pytest-bdd package on openSuSE Tumbleweed

Information for package python39-pytest-bdd:
--------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python39-pytest-bdd
Version : 5.0.0-1.12
Arch : noarch
Vendor : openSUSE
Installed Size : 244.1 KiB
Installed : No
Status : not installed
Source package : python-pytest-bdd-5.0.0-1.12.src
Upstream URL : https://github.com/pytest-dev/pytest-bdd
Summary : BDD for pytest
Description :
BDD library for the py.test runner
pytest-bdd implements a subset of Gherkin language for the automation of the project
requirements testing and easier behavioral driven development.
Unlike many other BDD tools it doesn't require a separate runner and benefits from
the power and flexibility of the pytest. It allows to unify your unit and functional
tests, easier continuous integration server configuration and maximal reuse of the
tests setup.
Pytest fixtures written for the unit tests can be reused for the setup and actions
mentioned in the feature steps with dependency injection, which allows a true BDD
just-enough specification of the requirements without maintaining any context object
containing the side effects of the Gherkin imperative declarations.