How to Install and Uninstall python312-fudge Package on openSuSE Tumbleweed
Last updated: December 28,2024
1. Install "python312-fudge" package
Please follow the guidance below to install python312-fudge on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python312-fudge
Copied
2. Uninstall "python312-fudge" package
Please follow the steps below to uninstall python312-fudge on openSuSE Tumbleweed:
$
sudo zypper remove
python312-fudge
Copied
3. Information about the python312-fudge package on openSuSE Tumbleweed
Information for package python312-fudge:
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-fudge
Version : 1.1.1-6.12
Arch : noarch
Vendor : openSUSE
Installed Size : 511.1 KiB
Installed : No
Status : not installed
Source package : python-fudge-1.1.1-6.12.src
Upstream URL : https://github.com/fudge-py/fudge
Summary : Module for replacing real objects with fakes (mocks, stubs, etc) while testing
Description :
Fudge is a Python module for using fake objects (mocks and stubs) to test real ones.
In readable Python code, you declare what methods are available on your fake and
how they should be called. Then you inject that into your application and start
testing. This declarative approach means you don't have to record and playback
actions and you don't have to inspect your fakes after running code. If the fake
object was used incorrectly then you'll see an informative exception message
with a traceback that points to the culprit.
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-fudge
Version : 1.1.1-6.12
Arch : noarch
Vendor : openSUSE
Installed Size : 511.1 KiB
Installed : No
Status : not installed
Source package : python-fudge-1.1.1-6.12.src
Upstream URL : https://github.com/fudge-py/fudge
Summary : Module for replacing real objects with fakes (mocks, stubs, etc) while testing
Description :
Fudge is a Python module for using fake objects (mocks and stubs) to test real ones.
In readable Python code, you declare what methods are available on your fake and
how they should be called. Then you inject that into your application and start
testing. This declarative approach means you don't have to record and playback
actions and you don't have to inspect your fakes after running code. If the fake
object was used incorrectly then you'll see an informative exception message
with a traceback that points to the culprit.