PHPUnit not working with Laravel 5

Question

I just installed a fresh Laravel 5 project, my first one on this version. PHPUnit is supposed to be out of the box with the framework and every tutorials I saw just say to type phpunit within the project folder to launch the Unit Tests.

I checked and PHPUnit is in the composer.json, I also did a composer install and composer update just in case it wouldn't be here

website(master)$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Removing phpunit/phpunit (4.6.1)
  - Installing phpunit/phpunit (4.6.2)
    Downloading: 100%

But it just doesn't work phpunit isn't recognized at all

 website(master)$ phpunit
-bash: phpunit: command not found

Seems like nobody got this problem before as I Googled it. I hope I'm not doing any stupid mistake. Any idea or suggestion ? Thanks guys ;)

@Laurent it's not uncommon to have PHPUnit installed globally on your system so you can run `phpunit` from anywhere — Phil, Apr 08 '15 at 01:43

score 52 · Accepted Answer · answered Apr 08 '15 at 01:44

52

I didn't install PHPUnit globally and didn't define the path. So for anyone who would have same problem :

composer global require phpunit/phpunit
composer global require phpunit/dbunit

Then you add this to you ~/.bash_profile or ~/.profile

export PATH=~/.composer/vendor/bin:$PATH

answered Apr 08 '15 at 01:44

Laurent

2,284
2
21
41

9

For anyone using phpunit globally: might this approach have the downside of always testing with the same version of phpunit VS testing with the one defined by the project composer.json file (as the answer of atul_systematix states)? Or isn't this really an issue to worry about? – Bert H Nov 06 '17 at 10:19

score 17 · Answer 2 · edited Nov 06 '17 at 10:33

17

This occurs when you don't have phpunit installed globally.

Run this command to use the local version (installed with composer):

vendor/bin/phpunit

edited Nov 06 '17 at 10:33

Bert H

1,087
1
15
29

answered Dec 14 '16 at 06:56

atul_systematix

253
3
12

6

While this code snippet may solve the question, [including an explanation](http://meta.stackexchange.com/questions/114762/explaining-entirely-code-based-answers) really helps to improve the quality of your post. Remember that you are answering the question for readers in the future, and those people might not know the reasons for your code suggestion. – DimaSan Dec 14 '16 at 07:50

score 11 · Answer 3 · answered Mar 29 '19 at 04:56

11

in windows machine the command is different please use this command

php vendor/phpunit/phpunit/phpunit

orignal source

answered Mar 29 '19 at 04:56

Sunil Kumar

759
7
17

How we can make it less as it is very long,do you know any way to do this in Windows 10? – Magento Dev Aug 25 '20 at 12:20

score 3 · Answer 4 · answered Feb 04 '19 at 11:15

3

You can run this command in cmd before running phpunit command:

doskey phpunit="vendor/bin/phpunit"

And if you are lazy as I am, you can run this one:

doskey pu="vendor/bin/phpunit"

answered Feb 04 '19 at 11:15

Saeid

1,269
1
9
12

after restarting cmd I have to repeat this command, how make it work for everytime? – keizah7 Jul 16 '19 at 15:44
Yes dude, don't be lazy as I am and run the command before each new cmd session ;) – Saeid Jul 18 '19 at 20:31
doskey on Windows is very similar to alias on Linux – Yevgeniy Afanasyev Jun 07 '22 at 02:57

score 2 · Answer 5 · answered Oct 10 '19 at 14:30

2

for people who have WINDOWS 7, use the .\vendor\bin\phpunit command instead of ./vendor/bin/phpunit

answered Oct 10 '19 at 14:30

mohamed chakir

21
1

score 0 · Answer 6 · answered Jan 28 '20 at 09:08

Run the command

composer config --list --global | grep -w home

You can find the find the [home] with composer path, similar to this one.

[home] /home/example_username/.config/composer

The path ~/.config/composer is where composer global packages are installed. Next run the command...

export PATH=~/.config/composer/vendor/bin:$PATH

score 0 · Answer 7 · answered Jun 07 '22 at 03:19

0

I made a permanent link to my phpunit like this

echo 'alias phpunit=vendor/bin/phpunit' >> ~/.bash_aliases

now phpunit is working by itself and stays even after I restart the terminal

answered Jun 07 '22 at 03:19

Yevgeniy Afanasyev

37,872
26
173
191

score -1 · Answer 8 · answered Nov 19 '15 at 04:16

-1

Include this line on your composer.json

"phpunit/phpunit": "4.0.*",

Run composer update. You should be able to run the following command on your Laravel directory.

vendor/bin/phpunit

answered Nov 19 '15 at 04:16

Kent Aguilar

5,048
1
33
20

PHPUnit not working with Laravel 5

8 Answers8