phpunit即使没有测试也给出错误（Laravel）

Question

Hi I just download phpunit.phar in my laravel project (which I already developed partly). I started by doing a simple

php phpunit.phar

but it outputs things like whole viewfiles with at the end:

 {"error":{"type":"ErrorException","message":"Undefined variable: currency","file":"C:\\wamp\\www\\project.dev\\app\\views\\front\\settings.php","line":79}}

This is not even a test and the code works when testing out in the browser. I am also using the default phpunit configuration file shipped with laravel.

EDIT: the code

<label class="radio">
<input type="radio" name="settings_currency" id="set_curr_<?=$currency->id?>" value="<?=$currency->id?>" checked>
<span class="symbol"><?=$currency->symbol?></span>
<?=$currency->name?>
<span><?=$currency->abbr?></span>
</label>

Answer 1

You cannot simply run PHPUnit and expect it to test something useful. You have to configure it!

When run, PHPUnit scans the current directory and all subdirectories for PHP files, includes them and checks if there are any test classes defined that can be run. Including your view files will execute them without context, ie you'll get the complete echo and notices from any used, but currently undefined variables.

As a starter, create a "phpunit.xml" in the same directory you are starting PHPUnit. Read the documentation on how to create it's contents. First and foremost you need to specify which directory to scan for test classes with the <testsuites> element.

Answer 2

the code works when testing out in the browser.

Well, as you might can imagine, only having some "code working in the browser" must not mean the code is error-free.

See the error message again you get:

Undefined variable: currency

So what you experience here can be explained shortly as: PHPUnit is more strict with your code than you are. It will mark warnings you didn't care about in the past, like in this example Undefined Variables .

So now learn about how to define variables and why using Undefined Variables is certainly your Problem and then you will easily understand as well why PHPUnit checks for those.

You can as well lower your expectations by lowering the quality standards PHPUnit applies when running tests by configuring it: Appendix C. The XML Configuration File

However, with the default config, it's just giving you that error and you should just fix it. PHPUnit does not only run tests, it also executes some code and deals with issues related to executing code, like getting Warnings, Errors and Notices.

It's you who need to deal with that if you execute phpunit. Otherwise, just step back and do not execute it :)

I am also using the default phpunit configuration file shipped with laravel.

Yes you are. That is why tests are run. And that's why you're caught in the act of using Undefined Variables .

---

See as well:

• Unit Testing - Laravel Documentation
• Reference - What does this error mean in PHP?
• PHP: “Notice: Undefined variable” and “Notice: Undefined index”