Download the PHP package damianlewis/octobertesting-plugin without Composer

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

October Testing

Enables the use of the Laravel testing frameworks within October CMS.

Usage

Installation

Install via Composer:

Plugin Feature & Unit Tests

To test plugins, create a tests folder within the plugin base folder and copy the phpunit.xml file to this location, for example, /plugins/acme/blog/tests/phpunit.xml. Create sub folders for feature and unit tests, for example, /plugins/acme/blog/tests/feature/ and /plugins/acme/blog/tests/unit/. Then in the tests folders, create tests following the principles used for Laravel testing. Test suites have been configured within the phpunit.xml file for feature and unit tests.

When creating tests, use the alternative Tests\PluginTestCase class. This alternative class doesn't make use of an in memory database, allowing you to choose what database you wish to use for testing. See example below.

Laravel Dusk

To make use of Laravel Dusk with OctoberCMS, run the dusk:install Artisan command:

Then use Dusk as you would with Laravel, see Laravel Dusk. For example, to run tests from the CLI use the dusk Artisan command:

Authentication

To make use of the login and loginAs authentication methods, an object containing the login and password for the user is expected. To provide the default/admin user account, you can override the user method in the Tests\DuskTestCase class as follows:

Screenshots

To create browser screenshots add the --window-size argument to the ChromeOptions->addArguments method as shown below:


All versions of octobertesting-plugin with dependencies

PHP Build Version
Package Version
Requires php Version >=7.0
composer/installers Version ~1.0
october/system Version >=1.0.420
laravel/dusk Version ~2.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 damianlewis/octobertesting-plugin contains the following files

Loading the files please wait ....