How to Install and Uninstall perl-Test-HTTP-MockServer Package on openSUSE Leap

Last updated: November 08,2024

1. Install "perl-Test-HTTP-MockServer" package

This tutorial shows how to install perl-Test-HTTP-MockServer on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install perl-Test-HTTP-MockServer

2. Uninstall "perl-Test-HTTP-MockServer" package

Here is a brief guide to show you how to uninstall perl-Test-HTTP-MockServer on openSUSE Leap:

$ sudo zypper remove perl-Test-HTTP-MockServer

3. Information about the perl-Test-HTTP-MockServer package on openSUSE Leap

Information for package perl-Test-HTTP-MockServer:
--------------------------------------------------
Repository : Main Repository
Name : perl-Test-HTTP-MockServer
Version : 0.0.1-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 25.3 KiB
Installed : No
Status : not installed
Source package : perl-Test-HTTP-MockServer-0.0.1-bp155.1.4.src
Upstream URL : https://metacpan.org/release/Test-HTTP-MockServer
Summary : Implement a mock HTTP server for use in tests
Description :
Sometimes, when writing a test, you don't have to oportunity to do
dependency injection of the type of transport used in a specific API.
Sometimes that code willl unequivocally always use actual HTTP and the only
control you have is over the host and port to which it will connect.
This class offer a simple way to mock the service being called. It does
that by binding to a random port on localhost and allowing you to inspect
which port that was. Using a random port means that this can be used by
tests running in parallel on the same host.
The socket will be bound and listened on the main test process, such that
the lifetime of the connection is defined by the lifetime of the test
itself.
Since the socket will be already bound and listened to, the two conntrol
methods (start_mock_server and stop_mock_server) fork only for the accept
call, which means that it is safe to call start and stop several times
during the test in order to change the expectations of the mocked code.
That allows you to easily configure the expectations of the mock server
across each step of your test case. On the other hand, it also means that
no state is shared between the code running in the mock server and the test
code.