Download the PHP package try/test without Composer

On this page you can find all versions of the php package try/test. 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 try/test

Informations about the package test

tapping

Atomic testing

Build Status Technical dept

Install

Usage

API

Functions

test($description, $test)

Function to run an atomic test and output it's status.

Arguments
Argument Type Description
$description string The description what the test case is supposed to do. Will be output on test run with an indication of success or failure.
$test callable The test case encapsulated in an callable. The test case will be forked as a child process, so anything in the callable is encapsulated from the parent process. Needs to exit(1) or a thrown Exception to indicate test as failed (throwing an exception will render an error block). exit(0) or just nothing will mark the test as passed.
CLI Flags

Since the runner of the tests is pure php, it is necessary for the usage in CI pipelines or other build systems that the main test process exists with an error code. Tapping has a build in feature for this.

By providing script flags on script call, e.g.

The test run will exit the whole process with -1, as soon as the first test fails.

Flag aliases which trigger such behaviour are --build and -b.

In addition to the build flag, it is also possible to provide an --quite (short -q) flag to suppress fail information (File, Line and error that occured).

todo($description)

Function to show a notation for a test case, not yet written. As reminder or note or whatever.

Arguments
Argument Type Description
$description string The description of the test to be written.

$t

The $t argument, is a container for prediction and likewise functions.

Predictions

License

GPL-2.0 © Willi Eßer, Felix Buchheim

All versions of test with dependencies

PHP Build Version
Package Version
Requires php Version >=7.0
troublete/task Version ^2.1
troublete/crayon Version ^1.1
troublete/load Version ^1.0
try/predict-output Version ^1.0
try/predict-exception Version ^1.0
try/predict-is 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 try/test contains the following files

Loading the files please wait ....