PHP download

Download the PHP package auto1-oss/php-behat-context-wiremock without Composer

On this page you can find all versions of the php package auto1-oss/php-behat-context-wiremock. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download auto1-oss/php-behat-context-wiremock
More information about auto1-oss/php-behat-context-wiremock
Files in auto1-oss/php-behat-context-wiremock

Vendor auto1-oss
Package php-behat-context-wiremock
Short Description Behat context for Wiremock support
License Apache-2.0

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.

Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
To use Composer is sometimes complicated. Especially for beginners.
Composer needs much resources. Sometimes they are not available on a simple webspace.
If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.

Please rate this library. Is it a good library?

Informations about the package php-behat-context-wiremock

php-behat-context-wiremock

This package provides a seamless integration between Behat tests and Wiremock, offering a straightforward method for mocking HTTP requests. It acts as a conduit between Behat scenarios and a Wiremock instance, enabling the creation of HTTP request expectations and mock responses without sacrificing Wiremock's inherent flexibility.

Configuration Example

Below is an example of how to configure the Wiremock context within your Behat setup:

baseUrl: The URL of your Wiremock instance.
stubsDirectory: The base directory for Wiremock stubs. This cannot be specified if stubsDirectoryIsFeatureDirectory is enabled.
cleanWiremockBeforeEachScenario: If true, Wiremock will be cleared before each scenario.
allStubsMatchedAfterEachScenario: If true, ensures that all stubs are matched after each scenario.
stubsDirectoryIsFeatureDirectory: If true, stubs will be sourced from the directory of a Behat feature file. This can only be enabled if stubsDirectory is not specified.
Note: stubsDirectory and stubsDirectoryIsFeatureDirectory cannot be used simultaneously.

Docker Integration

For those running Behat within Docker, integrating a Wiremock container is straightforward. The following configuration ensures that your tests wait for Wiremock to be fully initialized before running:

Context Steps

Defining Wiremock Stubs

Given wiremock stub: This step allows you to define a Wiremock stub directly within your scenario.

Example:
Given wiremock stubs from {file}: This step loads stubs from a specified file or directory and sends them to Wiremock.

Example:
Given wiremock stubs from {file} should be called {count} times: This step loads stubs from a specified file or directory, sends them to WireMock and also allows you to verify that the stub is called the specified number of times.

Example:
Given wiremock stubs from {file} should be called once: This step loads stubs from a specified file or directory, sends them to WireMock and also allows you to verify that the stub is called once.

Example:
Given wiremock stubs from {file} should be called at least {count} times: This step loads stubs from a specified file or directory, sends them to WireMock and also allows you to verify that the stub is called at least the specified number of times.

Example:
Given wiremock stubs from {file} should be called at most {count} times: This step loads stubs from a specified file or directory, sends them to WireMock and also allows you to verify that the stub is not called more than the specified number of times.

Example:

Managing Wiremock State

Given clean wiremock: Resets Wiremock to its initial state.

Example:

Validating Stubs

Then all stubs should be matched: Ensures that all added stubs were matched at least once and fails if there were any unexpected (unmatched) calls to Wiremock.

Example:

This integration aims to simplify the process of testing HTTP interactions within your Behat scenarios, leveraging Wiremock's powerful mocking capabilities to enhance your testing suite.

All versions of php-behat-context-wiremock with dependencies

PHP Build Version

Package Version

Version v1.0.3 Release 26. Nov 2024
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of php-behat-context-wiremock from vendor auto1-oss

Requires php Version >=8.0
behat/behat Version >=3.0
symfony/http-client Version >=3.0
symfony/contracts Version >=1.0

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package auto1-oss/php-behat-context-wiremock contains the following files

Loading the files please wait ....