Download the PHP package knectar/behat-ci without Composer

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

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 behat-ci

behat-ci

Scrutinizer Code Quality

Introduction

Behat continuous integration CLI is an efficient way to manage Behat configurations and have Behat testing run automatically when a project is updated. It will also generate a custom Behat.yml configuration file for you. All you have to do is specify the profiles.

System requirements

Installation

  1. Include behat-ci in your global composer.json with composer global require knectar/behat-ci
  2. Run composer global update to install (No database configuration needed.)
  3. Run composer install in the directory where the app was saved. (usually /home/user/.composer/vendor/knectar/behat-ci/app)
  4. Update your system PATH to include the application's app directory (path/to/global/.composer/vendor/knectar/behat-ci/app)
  5. That is all, we can now run this application's commands!

Configuration

The smooth running of behat-ci relies on several files working in synchrony.

bhqueue.txt is a simple text file that keeps track of when tests are scheduled to be run, written to by the bh schedule command.

profiles.yml is a list of device profiles as well as default Behat configuration. Feel free to add more and customize according to the current standards and what is available on sauce labs. See the sample files for use as a template.

projects.yml is a list of your projects that to run tests against. It will contain an entry per project, structured as follows:

Note: by default, projects.yml, profiles.yml, bhqueue, and bhqueuelog are located in the /etc/behat-ci/ directory. Trigger will look for profiles.yml and projects.yml to be set up in /etc/behat-ci or in the user's home directory. Otherwise the absolute paths to the files must be set in config.yml so the command knows where to look.

Usage

For details on the commands in the console, simply run

bh

The application relies on 2 key commands,

bh schedule

Is to be called when changes are pushed (or manually). This command will

  1. Update bhqueue.txt, which tells the application that tests need to be run.

  2. Generate the .yml configuration file required to run customized Behat configurations. This file will be stored in /tmp and disposed of by the 'trigger' command. You may use behat-ci to just generate behat.yml files and execute behat testing manually by running bh schedule $projname -b $branchname followed by behat -c /tmp/project_env.yml

    bh trigger Is meant to be called periodically (every minute) by cron on the server. It checks bhqueue to see if a change has been made in the project and if testing needs to be done. It will run the Behat tests as needed with the specified flags/parameters.

To run tests manually in a single command, run

bh test

with the same input arguments as bh schedule, and the application will perform schedule and trigger consecutively.

All versions of behat-ci with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.9
symfony/symfony Version 2.7.*
symfony/monolog-bundle Version ~2.4
incenteev/composer-parameter-handler Version ~2.0
symfony/console Version ^2.7
symfony/yaml Version ^2.7
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 knectar/behat-ci contains the following files

Loading the files please wait ....