Download the PHP package interactive-solutions/zf-behat without Composer
On this page you can find all versions of the php package interactive-solutions/zf-behat. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package zf-behat
InteractiveSolutions/Zf-behat
Description
A set of predefined step definitions to handle the most common cases when testing a REST API through Zend Framework.
Setup
Add it to your behat.yml file as follows:
The available configurable parameters for this module are:
config_file- path to your autoload configuration file for your api (defaultconfig/application.config.php).api_url- base url of your api (defaulthttp://localhost).mailcatcher_url- the url to your mailcatcher server (defaulthttp://mailcatcher:1080).
Enable the module InteractiveSolutions\ZfBehat in your autoload config file.
Available contexts
The module contains a bunch of different steps for various types of testing, all of which can be seen below.
Please see each individual context for further reference.
ApiContext
This context contains all step definitions for various api calls.
BernardContext
Context containing basic steps for testing an application using bernard to run background tasks.
DatabaseContext
Manages the Doctrine entity manager. Contains a single step that should be
run as a background in each feature file (Given a clean database). This step
drops and rebuilds the entire database, allowing a clean database before each scenario.
EntityFixtureContext
Contains various steps for setting up a scenario by creating entities.
MailcatcherContext
Manages mail testing using the specified mailcatcher_url. Useful for testing
if activation emails (and similar) are sent.
ZfrOAuthContext
Contains steps needed for zfr-oauth authentication/authorization.
Configuring default parameters
Paste the interactive-solutions.zf-behat.global.php.dist into your config.
UserOptions are used to specify default parameters for users in the steps
defined in the ZfrOAuthContext.
EntityOptions are used to specify default parameters for entities created
and manages through the EntityFixtureContext and ApiContext.
Things to note with EntityOptions
- route is automatically prefixed with
/, somatchesbecomes/matches - aliases are used to create an alias for a configured entity
- defaultProperties are also used as default parameters when sending api requests
Using aliases in TableNodes or PyStringNode
If Alias does exist, %Alias:FieldName% is replaced with the FieldName of the Alias entity
You can also reference only the alias, if so, it will use the primary key of the entity.
License
Copyright (c) 2016 Interactive Solutions Bodama AB
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
