Download the PHP package richcongress/unit-bundle without Composer

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

Getting Started With RichCongressUnitBundle

This version of the bundle requires Symfony 4.4+ and PHP 7.3+.

Package version Build Status Coverage Status contributions welcome

The unit-bundle provides is suite for application testing. It provides wrappers to isolate tests, various test cases to avoid code redundancy and a easy fixtures management.

This bundle is a fork of the chaplean/unit-bundle.

Quick start

The unit-bundle requires almost no configuration but provides useful tools to test your code. Here is an basic example:

Table of content

  1. Installation
  2. Getting started
    • Configuration
    • Available test cases
      • CommandTestCase
      • ConstraintTestCase
      • ControllerTestCase
      • RepositoryTestCase
      • VoterTestCase
    • Using the annotations
    • Creating fixtures
    • Overriding services with stub services
    • Use dynamic mocks (legacy)
    • Available default service stubs
    • Role provider
  3. Versioning
  4. Contributing
  5. Hacking
  6. License

1. Installation

This version of the bundle requires Symfony 4.4+ and PHP 7.3+.

1.1 Composer

1.2 Bundles declaration

After the installation, make sure that those 4 bundles are declared correctly within the Kernel's bundles list.

1.3 Declare the PHP Extension

First and foremost, declare the PHPUnitExtension in the phpunit.xml.dist:

1.4 Mandatory configuration

By default, the bundle configures everything on its own but if the config has been overriden somewhere, you can override it back to the default by importing the configuration:

Or configure manually doctrine with something like this:

2. Getting started

3. Versioning

unit-bundle follows semantic versioning. In short the scheme is MAJOR.MINOR.PATCH where

  1. MAJOR is bumped when there is a breaking change,
  2. MINOR is bumped when a new feature is added in a backward-compatible way,
  3. PATCH is bumped when a bug is fixed in a backward-compatible way.

Versions bellow 1.0.0 are considered experimental and breaking changes may occur at any time.

4. Contributing

Contributions are welcomed! There are many ways to contribute, and we appreciate all of them. Here are some of the major ones:

As a reminder, all contributors are expected to follow our Code of Conduct.

5. Hacking

You might use Docker and docker-compose to hack the project. Check out the following commands.

6. License

unit-bundle is distributed under the terms of the MIT license.

See LICENSE for details.


All versions of unit-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=7.3
ext-json Version *
brianium/paratest Version ^3.1
dama/doctrine-test-bundle Version ^6.3
doctrine/doctrine-bundle Version ^2.0
doctrine/doctrine-fixtures-bundle Version ^3.2
doctrine/orm Version ^2.6
liip/functional-test-bundle Version ^3.0
liip/test-fixtures-bundle Version ^1.0
mockery/mockery Version ^1.0
phpunit/phpunit Version ^7.5
symfony/config Version ^4.0
symfony/console Version ^4.0
symfony/dependency-injection Version ^4.0
symfony/phpunit-bridge Version ^4.0
symfony/serializer Version ^4.0
symfony/validator Version ^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 richcongress/unit-bundle contains the following files

Loading the files please wait ....