Test your Laravel applications with phpspec

Overview

phpspec Laravel Extension

phpspec extension for testing Laravel applications.

Build Status Latest Stable Version Total Downloads License

Versions

Depending on the version of Laravel and/or Phpspec you're using, you'll want to make sure that you're using the version of this package that's right for you. Use the table below to pick the right one.

PHP Version Package Version Laravel Version Phpspec Version
>=5.3.0 ^v1.2 ^v4.1 ^v2.0
>=5.4.0 ^v2.0 v5.0-v5.3 ^v2.1
>=5.6.0 ^v3.0 ^v5.1-v5.4 ^v3.0
>=7.0.0 ^v4.0 ^v5.4 ^v4.0

Installation

Install the package with composer:

composer require --dev "benconstable/phpspec-laravel:~4.0"

then add this to your phpspec.yml:

extensions:
  PhpSpec\Laravel\Extension\LaravelExtension: ~

You can take a look at example.phpspec.yml for a good set of sensible phpspec defaults for a Laravel project.

Why this extension?

This extension provides you with a bootstrapped Laravel environment when writing your phpspec tests.

It allows you to make use of some of the nice features that Laravel provides, like class aliases and helper functions, without being hindered by your testing framework.

This extension is not a swap-in replacement for Laravel's built in PHPUnit setup. If you'd like integration and/or functional tests, please use that, Behat, or Codeception.

Configuration

Testing environment

By default, the extension bootstraps Laravel in the testing environment. You can change this to production (or whatever you like) by setting:

extensions:
  PhpSpec\Laravel\Extension\LaravelExtension:
    testing_environment: "production"

in your phpspec.yml.

App bootstrap path

By default, the extension will bootstrap your app by looking for bootstrap/app.php in the directory above vendor/. This is the default location that Laravel provides.

You can manually specify the path to the bootstrap file if you're using a non-standard installation, like so:

extensions:
  PhpSpec\Laravel\Extension\LaravelExtension:
    framework_path: "/non/standard/laravel/setup/app.php"

You can specify either an absolute path (use leading slash), or a path relative to the vendor/ directory.

Usage

Testing without Laravel

If you're not using any code specific to the Laravel environment, then you don't need to do anything differently. Just write your phpspec tests as normal!

Testing with Laravel

If you want to take advantage of Laravel's aliases, or use some of its helper functions, extend your specs from PhpSpec\Laravel\LaravelObjectBehavior. This will prevent errors when testing.

For example, this class uses an alias:

<?php
namespace App;

use Inspiring;

class MyInspiring extends Inspiring
{
    public function quoteBackwards()
    {
        return strrev(parent::quote());
    }
}

and without extending from PhpSpec\Laravel\LaravelObjectBehavior:

<?php
namespace spec\App;

use PhpSpec\ObjectBehavior;

class MyInspiringSpec extends ObjectBehavior
{
    function it_inspires_backwards()
    {
        $this->quoteBackwards()->shouldBeString();
    }
}

you'll get Fatal error: Class 'Inspiring' not found.... But extending from PhpSpec\Laravel\LaravelObjectBehavior:

<?php
namespace spec\App;

use PhpSpec\Laravel\LaravelObjectBehavior;

class MyInspiringSpec extends LaravelObjectBehavior
{
    function it_inspires_backwards()
    {
        $this->quoteBackwards()->shouldBeString();
    }
}

you'll get ✔ inspires backwards.

and this class uses a helper function:

<?php
namespace App;

class MyEncryptor
{
    public function encrypt($arg)
    {
        return bcrypt($arg);
    }
}

and without extending from PhpSpec\Laravel\LaravelObjectBehavior:

<?php
namespace spec\App;

use PhpSpec\ObjectBehavior;

class MyEncryptor extends ObjectBehavior
{
    function it_encrypts_a_string()
    {
        $this->encrypt()->shouldBeString();
    }
}

you'll get Fatal error: Call to a member function make() on a non-object.... But extending from PhpSpec\Laravel\LaravelObjectBehavior:

<?php
namespace spec\App;

use PhpSpec\Laravel\LaravelObjectBehavior;

class MyEncryptor extends LaravelObjectBehavior
{
    function it_encrypts_a_string()
    {
        $this->encrypt()->shouldBeString();
    }
}

you'll get ✔ encrypts a string.

Accessing the IoC container

If you need to access the Service Container in your specs, just use the app() helper!

Learning more about phpspec and Laravel

Laracasts has some great guides on phpspec and Laravel. 'Laravel, phpspec and refactoring' is a good starting point; it shows how you should use phpspec with Laravel, and covers the basics of writing tests (and it's free!).

Contributing

See CONTRIBUTING.md.

License

MIT © Ben Constable. See LICENSE for more info.

Thanks

Thanks to...

  • @obrignoni for their great work in getting this extension working with Laravel 5
  • @Sam-Burns for their great work in getting this extension working with Phpspec v3 and v4
  • All of the other contributors and to everyone that's reported issues and bugs with the project
Comments
  • phpspec-laravel 5

    phpspec-laravel 5

    Thanks for this amazing package I used it a lots on my projects. There is any chance that you may upgrade this package for Laravel 5? I moved my project to L5 and I got really painful error running my specs. Thanks

    opened by fenos 44
  • Throwing an error on L5

    Throwing an error on L5

    I have just installed the plugin but when I try to run phpspec an error is thrown.

    [ErrorException]                                                                                                              
    Declaration of App\Providers\BusServiceProvider::boot() should be compatible with Illuminate\Support\ServiceProvider::boot() 
    

    Version of phpspec laravel is ~2.0@dev and for laravel ~5.0

    The class just doesn't initialize. But works fine if I switch the out LaravelObjectBehavior for ObjectBehavior

    Please assist.

    opened by prodeveloper 15
  • This broke when upgrading to Laravel 5.4

    This broke when upgrading to Laravel 5.4

    When running PHPSpec after upgrading to Laravel 5.4 returns the following:

    [ReflectionException]                                                   
    Class Illuminate\Foundation\Bootstrap\DetectEnvironment does not exist 
    

    Stack Trace:

    Exception trace:
     () at /home/simon/Code/thephysics.guide/vendor/laravel/framework/src/Illuminate/Container/Container.php:681
     ReflectionClass->__construct() at /home/simon/Code/thephysics.guide/vendor/laravel/framework/src/Illuminate/Container/Container.php:681
     Illuminate\Container\Container->build() at /home/simon/Code/thephysics.guide/vendor/laravel/framework/src/Illuminate/Container/Container.php:565
     Illuminate\Container\Container->make() at /home/simon/Code/thephysics.guide/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:702
     Illuminate\Foundation\Application->make() at /home/simon/Code/thephysics.guide/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:208
     Illuminate\Foundation\Application->bootstrapWith() at /home/simon/Code/thephysics.guide/vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Util/Laravel.php:89
     PhpSpec\Laravel\Util\Laravel->createApplication() at /home/simon/Code/thephysics.guide/vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Util/Laravel.php:54
     PhpSpec\Laravel\Util\Laravel->refreshApplication() at /home/simon/Code/thephysics.guide/vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Listener/LaravelListener.php:52
     PhpSpec\Laravel\Listener\LaravelListener->beforeSpecification() at n/a:n/a
     call_user_func() at /home/simon/Code/thephysics.guide/vendor/symfony/event-dispatcher/EventDispatcher.php:174
     Symfony\Component\EventDispatcher\EventDispatcher->doDispatch() at /home/simon/Code/thephysics.guide/vendor/symfony/event-dispatcher/EventDispatcher.php:43
     Symfony\Component\EventDispatcher\EventDispatcher->dispatch() at /home/simon/Code/thephysics.guide/vendor/phpspec/phpspec/src/PhpSpec/Runner/SpecificationRunner.php:50
     PhpSpec\Runner\SpecificationRunner->run() at /home/simon/Code/thephysics.guide/vendor/phpspec/phpspec/src/PhpSpec/Runner/SuiteRunner.php:56
     PhpSpec\Runner\SuiteRunner->run() at /home/simon/Code/thephysics.guide/vendor/phpspec/phpspec/src/PhpSpec/Console/Command/RunCommand.php:178
     PhpSpec\Console\Command\RunCommand->execute() at /home/simon/Code/thephysics.guide/vendor/symfony/console/Command/Command.php:262
     Symfony\Component\Console\Command\Command->run() at /home/simon/Code/thephysics.guide/vendor/symfony/console/Application.php:848
     Symfony\Component\Console\Application->doRunCommand() at /home/simon/Code/thephysics.guide/vendor/symfony/console/Application.php:189
     Symfony\Component\Console\Application->doRun() at /home/simon/Code/thephysics.guide/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:102
     PhpSpec\Console\Application->doRun() at /home/simon/Code/thephysics.guide/vendor/symfony/console/Application.php:120
     Symfony\Component\Console\Application->run() at /home/simon/Code/thephysics.guide/vendor/phpspec/phpspec/bin/phpspec:26
     {closure}() at /home/simon/Code/thephysics.guide/vendor/phpspec/phpspec/bin/phpspec:28
    
    opened by simonhunt 13
  • Cant seem to access laravel app within test?

    Cant seem to access laravel app within test?

    Just getting around to testing the latest build and something is not right here? Both of these tests produce errors

    Created a quick test

    function it_should_access_laravel() { var_dump(App::environment()); var_dump($this->laravel); }

    The first one kills testing The second produces

    notice: Trying to get property of non-object in /Users/mikee/Documents/Projects/putest/app/spec/putest/SomeTestSpec.php line 19
    opened by mikeerickson 13
  • Target [Illuminate\Contracts\Debug\ExceptionHandler] is not instantiable.

    Target [Illuminate\Contracts\Debug\ExceptionHandler] is not instantiable.

    Hey! I just installed this extension, but I can't get it to run. I followed the instructions in the README.

    This is the error I get (with stack trace)

     [Illuminate\Container\BindingResolutionException]
      Target [Illuminate\Contracts\Debug\ExceptionHandler] is not instantiable.
    
    
    
    Exception trace:
     () at /home/vagrant/Projects/wallz/vendor/laravel/framework/src/Illuminate/Container/Container.php:785
     Illuminate\Container\Container->build() at /home/vagrant/Projects/wallz/vendor/laravel/framework/src/Illuminate/Container/Container.php:656
     Illuminate\Container\Container->make() at /home/vagrant/Projects/wallz/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:613
     Illuminate\Foundation\Application->make() at /home/vagrant/Projects/wallz/vendor/laravel/framework/src/Illuminate/Container/Container.php:1231
     Illuminate\Container\Container->offsetGet() at /home/vagrant/Projects/wallz/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:231
     Illuminate\Foundation\Console\Kernel->reportException() at /home/vagrant/Projects/wallz/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:94
     Illuminate\Foundation\Console\Kernel->handle() at /home/vagrant/Projects/wallz/vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Util/Laravel.php:284
     PhpSpec\Laravel\Util\Laravel->createApplication() at /home/vagrant/Projects/wallz/vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Util/Laravel.php:95
     PhpSpec\Laravel\Util\Laravel->refreshApplication() at /home/vagrant/Projects/wallz/vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Listener/LaravelListener.php:56
     PhpSpec\Laravel\Listener\LaravelListener->beforeSpecification() at n/a:n/a
     call_user_func() at /home/vagrant/Projects/wallz/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:164
     Symfony\Component\EventDispatcher\EventDispatcher->doDispatch() at /home/vagrant/Projects/wallz/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:53
     Symfony\Component\EventDispatcher\EventDispatcher->dispatch() at /home/vagrant/Projects/wallz/vendor/phpspec/phpspec/src/PhpSpec/Runner/SpecificationRunner.php:50
     PhpSpec\Runner\SpecificationRunner->run() at /home/vagrant/Projects/wallz/vendor/phpspec/phpspec/src/PhpSpec/Runner/SuiteRunner.php:56
     PhpSpec\Runner\SuiteRunner->run() at /home/vagrant/Projects/wallz/vendor/phpspec/phpspec/src/PhpSpec/Console/Command/RunCommand.php:113
     PhpSpec\Console\Command\RunCommand->execute() at /home/vagrant/Projects/wallz/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:253
     Symfony\Component\Console\Command\Command->run() at /home/vagrant/Projects/wallz/vendor/symfony/console/Symfony/Component/Console/Application.php:882
     Symfony\Component\Console\Application->doRunCommand() at /home/vagrant/Projects/wallz/vendor/symfony/console/Symfony/Component/Console/Application.php:195
     Symfony\Component\Console\Application->doRun() at /home/vagrant/Projects/wallz/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:77
     PhpSpec\Console\Application->doRun() at /home/vagrant/Projects/wallz/vendor/symfony/console/Symfony/Component/Console/Application.php:126
     Symfony\Component\Console\Application->run() at /home/vagrant/Projects/wallz/vendor/phpspec/phpspec/bin/phpspec:26
    
    opened by onbjerg 9
  • L5 - phpspec dependency and outdated symfony/yaml error

    L5 - phpspec dependency and outdated symfony/yaml error

    If I have the following in composer.json under require-dev:

    "phpunit/phpunit": "~4.0",
    "phpspec/phpspec": "2.1.*@dev",
    "benconstable/phpspec-laravel": "~2.0"
    

    On running composer install I get this error:

    vagrant@homestead:~/Code/Private/bookie$ composer install
    Loading composer repositories with package information                                                                                                                             Installing dependencies (including require-dev)       Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - benconstable/phpspec-laravel 2.x-dev requires phpspec/phpspec 2.1.0-RC1 -> satisfiable by phpspec/phpspec[2.1.0-RC1].
        - benconstable/phpspec-laravel 2.x-dev requires phpspec/phpspec 2.1.0-RC1 -> satisfiable by phpspec/phpspec[2.1.0-RC1].
        - Conclusion: don't install phpspec/phpspec 2.1.0-RC1
        - Installation request for benconstable/phpspec-laravel ~2.0 -> satisfiable by benconstable/phpspec-laravel[2.x-dev].
    

    If I change phpspec to 2.1.0-RC1:

    "phpunit/phpunit": "~4.0",
    "phpspec/phpspec": "2.1.0-RC1",
    "benconstable/phpspec-laravel": "~2.0"
    

    Then composer install works but on running phpspec run the following error is thrown:

    vagrant@homestead:~/Code/Private/bookie$ phpspec run
    PHP Deprecated:  The ability to pass file names to Yaml::parse() was deprecated in 2.2 and will be removed in 3.0. Please, pass the contents of the file instead. in /home/vagrant/Code/Private/bookie/vendor/symfony/yaml/Symfony/Component/Yaml/Yaml.php on line 58
    PHP Stack trace:
    PHP   1. {main}() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/bin/phpspec:0
    PHP   2. Symfony\Component\Console\Application->run() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/bin/phpspec:24
    PHP   3. PhpSpec\Console\Application->doRun() /home/vagrant/Code/Private/bookie/vendor/symfony/console/Symfony/Component/Console/Application.php:126
    PHP   4. PhpSpec\Console\Application->loadConfigurationFile() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:67
    PHP   5. PhpSpec\Console\Application->parseConfigurationFile() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:117
    PHP   6. Symfony\Component\Yaml\Yaml::parse() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:159
    PHP   7. trigger_error() /home/vagrant/Code/Private/bookie/vendor/symfony/yaml/Symfony/Component/Yaml/Yaml.php:58
    
    Deprecated: The ability to pass file names to Yaml::parse() was deprecated in 2.2 and will be removed in 3.0. Please, pass the contents of the file instead. in /home/vagrant/Code/Private/bookie/vendor/symfony/yaml/Symfony/Component/Yaml/Yaml.php on line 58
    
    Call Stack:
        0.0006     226592   1. {main}() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/bin/phpspec:0
        0.2076    2397520   2. Symfony\Component\Console\Application->run() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/bin/phpspec:24
        0.2693    2762288   3. PhpSpec\Console\Application->doRun() /home/vagrant/Code/Private/bookie/vendor/symfony/console/Symfony/Component/Console/Application.php:126
        0.2834    2997576   4. PhpSpec\Console\Application->loadConfigurationFile() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:67
        0.2834    2997688   5. PhpSpec\Console\Application->parseConfigurationFile() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:117
        0.2938    3014568   6. Symfony\Component\Yaml\Yaml::parse() /home/vagrant/Code/Private/bookie/vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:159
        0.2941    3014952   7. trigger_error() /home/vagrant/Code/Private/bookie/vendor/symfony/yaml/Symfony/Component/Yaml/Yaml.php:58
    
    
    0 specs
    0 examples 
    0ms
    
    opened by cgrossde 8
  • PhpSpec 4

    PhpSpec 4

    Provides a version which works with PhpSpec 4, released recently.

    Removes builds testing in PHP 5, as this is no longer supported by PhpSpec.

    Removes builds testing in older versions of Laravel, as they are pinned to old 3.0.* versions of Symfony components. This means you cannot install PhpSpec 4 with Laravel < 5.4.

    opened by Sam-Burns 7
  • Laravel application not started?

    Laravel application not started?

    I am not sure what is the issue here is. As I understand, this plugin will create the Laravel application instance. That does not seem to be happening here?

    I have a spec

    
       function it_should_be_testing_environment()
        {
            $this->getEnvironment()->shouldBe('testing');
        }
    
    

    Which has a test.php as follows

    
    
    

    Execute the spec it just dies silently implying there is error in my test.php file

    What am I doing wrong here?

    opened by mikeerickson 5
  • Defining console_kernel_class causes issue with phpspec

    Defining console_kernel_class causes issue with phpspec

    If I set console_kernel_class: MyApp\Console\Kernel in my phpspec.yml, it causes phpspec to break. I start seeing the following message with all failing (but not passing) specs when I run "phpspec run":

      [InvalidArgumentException]     
      Command "run" is not defined.  
      Did you mean this?             
          schedule:run               
    
    Exception trace:
     () at ./vendor/symfony/console/Symfony/Component/Console/Application.php:549
     Symfony\Component\Console\Application->find() at ./vendor/symfony/console/Symfony/Component/Console/Application.php:192
     Symfony\Component\Console\Application->doRun() at ./vendor/symfony/console/Symfony/Component/Console/Application.php:126
     Symfony\Component\Console\Application->run() at ./vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:90
     Illuminate\Foundation\Console\Kernel->handle() at ./vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Util/Laravel.php:289
     PhpSpec\Laravel\Util\Laravel->createApplication() at ./vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Util/Laravel.php:95
     PhpSpec\Laravel\Util\Laravel->refreshApplication() at ./vendor/benconstable/phpspec-laravel/src/PhpSpec/Laravel/Listener/LaravelListener.php:56
     PhpSpec\Laravel\Listener\LaravelListener->beforeSpecification() at n/a:n/a
     call_user_func() at ./vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:164
     Symfony\Component\EventDispatcher\EventDispatcher->doDispatch() at ./vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:53
     Symfony\Component\EventDispatcher\EventDispatcher->dispatch() at ./vendor/phpspec/phpspec/src/PhpSpec/Runner/SpecificationRunner.php:50
     PhpSpec\Runner\SpecificationRunner->run() at ./vendor/phpspec/phpspec/src/PhpSpec/Runner/SuiteRunner.php:56
     PhpSpec\Runner\SuiteRunner->run() at ./vendor/phpspec/phpspec/src/PhpSpec/Console/Command/RunCommand.php:113
     PhpSpec\Console\Command\RunCommand->execute() at ./vendor/symfony/console/Symfony/Component/Console/Command/Command.php:253
     Symfony\Component\Console\Command\Command->run() at ./vendor/symfony/console/Symfony/Component/Console/Application.php:882
     Symfony\Component\Console\Application->doRunCommand() at ./vendor/symfony/console/Symfony/Component/Console/Application.php:195
     Symfony\Component\Console\Application->doRun() at ./vendor/phpspec/phpspec/src/PhpSpec/Console/Application.php:77
     PhpSpec\Console\Application->doRun() at ./vendor/symfony/console/Symfony/Component/Console/Application.php:126
     Symfony\Component\Console\Application->run() at ./vendor/phpspec/phpspec/bin/phpspec:26
    

    This behaviour was confirmed by @onbjerg in issue #31.

    The issue arose for me because I am using my custom Console\Kernel class to override the bootstrapping in order to use a custom Http\Request class.

    opened by hackel 4
  • Allow setting laravel path

    Allow setting laravel path

    It would be infinitely helpful to be able to set the laravel path in the phpspec.yml

    Then all my packages for laravel can be tested where it sits using a single laravel instance elsewhere. Suitable for 99% of testing needs (helpers, IoC, etc)

    opened by RyanThompson 4
  • call migrate:refresh on each app refresh

    call migrate:refresh on each app refresh

    This is useful so test data can be inserted into the DB without having to make sure everything is cleaned up at the end - just let the normal migrate up/down handle it.

    opened by aMoniker 4
  • Support for Laravel 6

    Support for Laravel 6

    Attempting to upgrade an application to Laravel 6 but running into the following dependency conflict: benconstable/phpspec-laravel v4.0.1 requires laravel/framework ^5.4

    opened by diggersworld 0
  • Support for phpSpec 5

    Support for phpSpec 5

    Hello,

    right now this plugin does not work when phpspec 5.0 is being used with PHP 7.2.9

    and we can not use 4.0 there as phpspec has a constraint of PHP <7.2.0

    opened by dakshhmehta 2
  • Feature/add support for custom env files

    Feature/add support for custom env files

    Added a feature to use custom .env files. It is done via phpspec configuration with testing_environment_file setting. The testing_environment_file will override the testing_environment setting.

    Purpose:

    • You can have a dummy env file without any credentials commited to the repo and used for spec testing,
    • You can specify a different database connection in that env file that, for example, uses SQLite in memory database.

    If you have any suggestions please feel free to message me as I'm more than happy to improve this. Thanks.

    opened by mrpiatek 2
Releases(v4.0.1)
Owner
Ben Constable
Principal Platform Engineer at Mediatonic. C#, Linux and Kubernetes. Building Fall Guys and other games played by millions of people
Ben Constable
⛽ Set of utilities to test Laravel applications powered by Octane.

⛽ Octane Testbench Set of utilities to test Laravel applications powered by Octane. Install Via Composer: composer require --dev cerbero/octane-testbe

Andrea Marco Sartori 35 Dec 7, 2022
Laravel-OvalFi helps you Set up, test, and manage your OvalFi integration directly in your Laravel App.

OvalFi Laravel Package Laravel-OvalFi helps you Set up, test, and manage your OvalFi integration directly in your Laravel App. Installation You can in

Paul Adams 2 Sep 8, 2022
🧑‍🔬 The missing assertions for your views in your Laravel applications.

Laravel View Assertions The missing assertions for your views in your Laravel applications. Installation You'll have to follow a couple of simple step

Sven Luijten 4 Dec 21, 2022
Package to easily test crudable controllers for Laravel based API

Laravel Crudable Test This package is very usefull to easily test crudable controllers. Installation You can install package via composer. Add reposit

null 2 Jul 27, 2022
Lightflows Technical Test

Installation git clone composer install cp .env.example .env php artisan key:generate setup database in .env php artisan migrate --seed php artisan pa

Parth Patel 92 Jun 27, 2022
🧾 Online test site with the human sciences theme. Using: HTML5, CSS3, Js., PHP7 and MySQL. 🚀

form-ciencias-humanas ?? Technologies Lunacy HTML5 CSS3 PHP7 MYSQL Animate.css Illustrations from icons8: Earth care from Anna Antipina Earth and Moon

Vinícius 1 Jan 9, 2022
Laravel Boilerplate provides a very flexible and extensible way of building your custom Laravel applications.

Laravel Boilerplate Project Laravel Boilerplate provides a very flexible and extensible way of building your custom Laravel applications. Table of Con

Labs64 848 Dec 28, 2022
This package lets you add uuid as primary key in your laravel applications

laravel-model-uuid A Laravel package to add uuid to models Table of contents Installation Configuration Model Uuid Publishing files / configurations I

salman zafar 10 May 17, 2022
Quickly identify controller methods with no route in your Laravel applications.

Orphan Controller Quickly identify controller methods with no route in your Laravel applications. Installation You can install the package via Compose

Ryan Chandler 16 Feb 18, 2022
Run patches migration style in your Laravel applications.

This package generates patch files in the same fashion Laravel generates migrations. Each file is timestamped with an up and a down method and is asso

Anthony Rappa 44 Sep 9, 2022
Ensure your Laravel applications keep a normal pulse

Ensure your Laravel applications keep a normal rhythm Laravel Defibrillator helps you ensure that aspects of your application that should be running a

Michael Dyrynda 148 Dec 20, 2022
Zarinpal is a laravel package to easily use zarinpal.com payment services in your applications

پکیج اتصال به درگاه پرداخت زرین پال zarinpal.com برای اتصال به درگاه پرداخت اینترنتی زرین پال و استفاده از api های آن می توانید از این پکیج استفاده کن

Rahmat Waisi 4 Jan 26, 2022
Integrate Astrel to your Laravel applications.

✨ Astrel Laravel Integrate Astrel to your Laravel applications. Astrel is a remote config orchestration application that enables you to change anythin

Sustainable Hustle 3 Jan 9, 2022
1Pilot.io, a universal dashboard to effortlessly manage all your Laravel applications

Website · Free Trial · Pricing · Documentation · API · Feedback · Support [You] What are you, strange being? [1Pilot] Greetings, traveller. I am 1Pilo

1Pilot 10 Nov 21, 2022
Jumpstart your web development journey with the HALT Stack Starter Kit, a one-command solution for creating dynamic, scalable, and clean web applications.

Welcome to the HALT Stack Starter Kit! This kit is designed to help you kickstart your web development projects using the HALT Stack, a powerful combi

HALT Stack 6 Jun 7, 2023
Nebula is a minimalistic and easy to use administration tool for Laravel applications, made with Laravel, Alpine.js, and Tailwind CSS.

Nebula Nebula is a minimalistic and easy to use administration tool for Laravel applications, made with Laravel, Alpine.js, and Tailwind CSS. Nebula m

Nebula 228 Nov 11, 2022
A simple `make:view` command for Laravel applications.

A simple make:view command for Laravel applications. Quickly generate a new Blade view from the console using artisan make:view. Installation You can

Ryan Chandler 10 Oct 17, 2022
Laravel package integrating PHP Flasher into Livewire applications

A powerful and flexible flash notifications system for PHP, Laravel, Symfony ?? PHP Flasher helps you to add flash notifications to your PHP projects.

PHP Flasher 9 Jul 5, 2022
A premade, easy to use local development setup to be used for authoring Laravel applications

Laravel Drydock This project is a premade, easy to use local development setup to be used for authoring Laravel applications. The deliverables of this

Alexander Trauzzi 19 Nov 11, 2022