How to Install and Uninstall python310-fudge Package on openSuSE Tumbleweed
Last updated: November 24,2024
1. Install "python310-fudge" package
This tutorial shows how to install python310-fudge on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python310-fudge
Copied
2. Uninstall "python310-fudge" package
Here is a brief guide to show you how to uninstall python310-fudge on openSuSE Tumbleweed:
$
sudo zypper remove
python310-fudge
Copied
3. Information about the python310-fudge package on openSuSE Tumbleweed
Information for package python310-fudge:
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-fudge
Version : 1.1.1-6.12
Arch : noarch
Vendor : openSUSE
Installed Size : 376.5 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 : python310-fudge
Version : 1.1.1-6.12
Arch : noarch
Vendor : openSUSE
Installed Size : 376.5 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.