Download the PHP package atoum/stubs without Composer

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

Informations about the package stubs

atoum stubs

atoum

Install it

Install extension using composer:

Use it

Once your IDE is correctly configured, the only thing you will have to do is use atoum through one of its alias:

atoum provides 3 aliases for the main test class, choose the one you prefer:

Once done, you will get full featured code-completion:

Why?

Why are the PHPdoc annotations part of an external repository?

Because we just don't want them in the middle of atoum's source code. It's not really useful there and it adds extra noise.

Moreover, if we use PHPDoc for the userland API we should also add annotations to every method of the internal API. Too much work for a small amount of added value.

Why are those annotations only working on atoum aliases?

Because we stored annotated code in an external repository, we would have to duplicate some classes to annotate them. Doing so would create duplicate classes and some IDEs will emit warnings.

We don't want to add extra noise while providing a good code-completion.

Why not annotating every public method?

Because they are not all meaningful in a test context. When you write unit tests with atoum, you will likely never call internal asserters' methods, even if they are public. They provide support for atoum so it can do its job well. But they won't help you in your everyday work.

Upgrade stubs

This will only update existing methods. To add new method you will require to do it manually! Think also to look at the tree of asserters to extends the class properly.

You probably also need to update classes/mageekguy/atoum/stubs/asserters.php with the new asserter set.

License

atoum stubs are released under the BSD-3-Clause License. See the bundled LICENSE file for details.

All versions of stubs with dependencies

PHP Build Version
Package Version
No informations.
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/stubs contains the following files

Loading the files please wait ....