How to Install and Uninstall perl-Test-Magpie Package on openSUSE Leap
Last updated: November 08,2024
1. Install "perl-Test-Magpie" package
Learn how to install perl-Test-Magpie on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-Test-Magpie
Copied
2. Uninstall "perl-Test-Magpie" package
Please follow the guidance below to uninstall perl-Test-Magpie on openSUSE Leap:
$
sudo zypper remove
perl-Test-Magpie
Copied
3. Information about the perl-Test-Magpie package on openSUSE Leap
Information for package perl-Test-Magpie:
-----------------------------------------
Repository : Main Repository
Name : perl-Test-Magpie
Version : 0.11-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 79.6 KiB
Installed : No
Status : not installed
Source package : perl-Test-Magpie-0.11-bp155.1.4.src
Upstream URL : https://metacpan.org/release/Test-Magpie
Summary : Mocking framework with method stubs and behaviour verification
Description :
Test::Magpie is a test double framework heavily inspired by the Mockito
framework for Java, and also the Python-Mockito project. In Mockito, you
"spy" on objects for their behaviour, rather than being upfront about what
should happen. I find this approach to be significantly more flexible and
easier to work with than mocking systems like EasyMock, so I created a Perl
implementation.
* Mock objects
Mock objects, represented by Test::Magpie::Mock objects, are objects that
pretend to be everything you could ever want them to be. A mock object can
have any method called on it, does every roles, and isa subclass of any
superclass. This allows you to easily throw a mock object around it will be
treated as though it was a real object.
* Method stubbing
Any method can be called on a mock object, and it will be logged as an
invocation. By default, method calls return 'undef' in scalar context or an
empty list in list context. Often, though, clients will be interested in
the result of calling a method with some arguments. So you may specify how
a method stub should respond when it is called.
* Verify interactions
After calling your concrete code (the code under test) you may want to
check that the code did operate correctly on the mock. To do this, you can
use verifications to make sure code was called, with correct parameters and
the correct amount of times.
* Argument matching
Magpie gives you some helpful methods to validate arguments passed in to
calls. You can check equality between arguments, or consume a general type
of argument, or consume multiple arguments. See
Test::Magpie::ArgumentMatcher for the juicy details.
-----------------------------------------
Repository : Main Repository
Name : perl-Test-Magpie
Version : 0.11-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 79.6 KiB
Installed : No
Status : not installed
Source package : perl-Test-Magpie-0.11-bp155.1.4.src
Upstream URL : https://metacpan.org/release/Test-Magpie
Summary : Mocking framework with method stubs and behaviour verification
Description :
Test::Magpie is a test double framework heavily inspired by the Mockito
framework for Java, and also the Python-Mockito project. In Mockito, you
"spy" on objects for their behaviour, rather than being upfront about what
should happen. I find this approach to be significantly more flexible and
easier to work with than mocking systems like EasyMock, so I created a Perl
implementation.
* Mock objects
Mock objects, represented by Test::Magpie::Mock objects, are objects that
pretend to be everything you could ever want them to be. A mock object can
have any method called on it, does every roles, and isa subclass of any
superclass. This allows you to easily throw a mock object around it will be
treated as though it was a real object.
* Method stubbing
Any method can be called on a mock object, and it will be logged as an
invocation. By default, method calls return 'undef' in scalar context or an
empty list in list context. Often, though, clients will be interested in
the result of calling a method with some arguments. So you may specify how
a method stub should respond when it is called.
* Verify interactions
After calling your concrete code (the code under test) you may want to
check that the code did operate correctly on the mock. To do this, you can
use verifications to make sure code was called, with correct parameters and
the correct amount of times.
* Argument matching
Magpie gives you some helpful methods to validate arguments passed in to
calls. You can check equality between arguments, or consume a general type
of argument, or consume multiple arguments. See
Test::Magpie::ArgumentMatcher for the juicy details.