Download the PHP package ecomdev/phpspec-magento-di-adapter without Composer

On this page you can find all versions of the php package ecomdev/phpspec-magento-di-adapter. 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 phpspec-magento-di-adapter

PHPSpec Magento 2.0 DI Adapter Build Status Coverage Status

This small PHPSpec extension allows you to test Magento 2.0 modules much more easier by utilizing generators of Magento\Framework\ObjectManager.

Why?

Reasons why not to use ObjectManager in PHPSpec examples:

  1. It is heavy and requires stubbing full file system in order to run a simple spec example.
  2. Depending on ObjectManager is a bad idea, as you don't want to test some-else DI overrides.
  3. Simple modules that do not require database do not need fully functional object manager
  4. Adapting your business logic to another framework will require from you only to materialize generated classes, instead of depending on the whole ObjectManager library.

Supported Generators

Installation

  1. Install via composer

  2. Add to your phpspec.yml

Usage

Make sure that when you write examples to specify fully qualified class name for auto-generated class.

This approach will not get you a desired result, as PHP by default looks for undefined classes within the same namespace. So instead of Magento\Catalog\Model\ProductFactory it will generate a class spec\Acme\CustomMagentoModule\Model\ProductFactory, that is definitely not a desired behavior.

In order to fix that make sure to specify fully qualified name in method signature or via use operator in the file header.

Contribution

Make a pull request based on develop branch


All versions of phpspec-magento-di-adapter with dependencies

PHP Build Version
Package Version
Requires php Version ~5.6|~7.0
magento/framework Version ~100.0
zendframework/zend-stdlib Version ~2.4.6
zendframework/zend-code Version ~2.4.6
mikey179/vfsstream Version ^1.6
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 ecomdev/phpspec-magento-di-adapter contains the following files

Loading the files please wait ....