Download the PHP package atoum/config-extension without Composer

On this page you can find all versions of the php package atoum/config-extension. 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?

Example code of atoum/config-extension

Informations about the package config-extension

atoum/config-extension Build Status

This extension will allow you to configure atoum using a YAML file and/or environnement variables.

Example

When using this extension, you can put a .atoum.yml on the root of your repository to configure atoum. Here is an exemple on how to tell atoum to look for unit tests in the tests/units/classes folder.

Install it

Install extension using composer:

Enable the extension using atoum configuration file:

Use it

Configuration reference

atoum.loop

boolean : enable/disable atoum's loop mode. Defaults on ATOUM_LOOP environnement variable.

Exemple:

atoum.debug

boolean : enable/disable atoum's debug mode. Defaults on ATOUM_DEBUG environnement variable.

Exemple:

atoum.verbosity

integer : value between 1 and 3 determining atoum's verbosity level'. Defaults on ATOUM_VERBOSITY environnement variable.

Exemple:

atoum.directories

array : List of directories where atoum will look for unit tests. Defaults on ATOUM_DIRECTORIES environnement variable (a coma separated list of directories).

atoum.reports

array : List of reports. Defaults on ATOUM_REPORTS environnement variable (a coma separated list of reports).

Example:

Possible values :

report.default

adds atoum's default reporter (when the reports key is defined, atoum's default reporter is no longer used).

report.coverage.clover

Adds a clover coverage reporter.

Path to were the report will be written could be configured using the coverage.clover.filename parameter.

report.xunit

Adds an xUnit reporter.

Path to were the report will be written could be configured using the xunit.filename parameter.

report.tap

Adds a TAP reporter.

report.vim

Adds a vim reporter.

report.nyancat

Adds a reporter that displays a nyancat.

report.santa

Adds a santa reporter.

atoum.fields

Fields allows you to customize reports. You can add fields for each report.

You need to add the report name as key, then add an array of fields.

This example adds the logo field to the default report :

field.logo

Displays atoum's logo at the begining of the report. Only works on cli reports.

field.logo.result

Displays atoum's logo at the end of the report. Only works on cli reports.

field.coverage.html

Generate an HTML coverage reports. Needs the php extension xdebug to be installed.

The project name in generated report and folder where the report will be generated could by configured with the coverage.html.directory and parameters.

parameters

You can customize the way reports or fields are generated using the parameters section on the .atoum.yml file.

Here is an example that changes the path where the xunit report is generated:

xunit.filename

Default value : xunit.xml.

Path were the xUnit report will be written in the report.xunit report.

The directory where the file is generated must exists, it will not be created by atoum.

coverage.html.directory

Default value : ./coverage.

Path to the folder where the HTML coverage files will be written. See field.coverage.html field.

project.name

Default value : atoum.

Will be used when generating the field.coverage.html field.

coverage.clover.filename

Default value : clover.xml.

Path where the clover report will be written in the report.clover report.

Links

License

config-extension is released under the BSD-3-Clause License. See the bundled LICENSE file for details.

atoum

All versions of config-extension with dependencies

PHP Build Version
Package Version
Requires atoum/atoum Version ^2.9||^3.0
symfony/yaml Version ^2.6||^3.0||^4.0
symfony/config Version ^2.6||^3.0||^4.0
symfony/dependency-injection Version ^2.6||^3.0||^4.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 atoum/config-extension contains the following files

Loading the files please wait ....