Download the PHP package backendtea/failuretest without Composer

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

Informations about the package failuretest

FailureTest

Allow failing PHPUnit tests and keep a close eye on issues until they are fixed.

Installation

Or simply copy the AllowFailure.php into your project and include it yourself.

Requirements

Usage

These traits make us of PHPUnits tearDown() function. If you override it, don't forget to call parent::tearDown();

Any test that has failed will show up as incomplete, with its original failure message attached. Once a test actually passes all its criteria, it will be marked as a failure, with an error message explaining you can move it to the normal tests.

AllowFailure

The AllowFailure trait gives you access to two annotations: @allowedFailure and @mustFail. Both work on method or class level.

@allowedFailure overrides @mustfail. So if both are present, be it on class or method, the test will not error if it succeeds.

Why

Instead of just creating an issue when finding a bug, someone can also contribute a failing test case. This makes sure the issue won't be forgotten, and it also allows another developer to better make sure they fixed the issue.

It can also serve as a nice 'todo' list, which can move with your code to another VCS if you so desire.

Contributing

If you find a bug, or want a feature, open an issue, or create a PR.

All tests in the Failure sub folder are supposed to fail, and the ones in the Success folder should not fail.

All versions of failuretest with dependencies

PHP Build Version
Package Version
Requires php Version ^5.6 || ^7.0
phpunit/phpunit Version ^5.0 || ^6.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 backendtea/failuretest contains the following files

Loading the files please wait ....