I have a newly installed Laravel 6.4 application running and now trying to get tests working with PHPunit. I want to make configuration changes in .env.testing but any changes in here seem to be ignored.
phpunit.xml contains this:
<php>
<server name="APP_ENV" value="testing"/>
<server name="BCRYPT_ROUNDS" value="4"/>
<server name="CACHE_DRIVER" value="array"/>
<server name="MAIL_DRIVER" value="array"/>
<server name="QUEUE_CONNECTION" value="sync"/>
<server name="SESSION_DRIVER" value="array"/>
</php>
And I have also have included $app->loadEnvironmentFrom('/var/www/api/.env.testing'); into tests/CreatesApplication.php createApplication() method. All paths are correct so I don't understand why it is not reading the file. I've found similar mentions of this issue when googling but none have helped me resolve the issue.
I am running PHPunit with the command vendor/bin/phpunit. Does anyone have suggestions on what I can try?
I have installed a fresh Laravel project. I tried to set different database for PHPUnit testing, by adding "DB_DATABASE" And adding "use DatabaseMigrations" trait inside the test..
<server name="APP_ENV" value="testing"/>
<server name="BCRYPT_ROUNDS" value="4"/>
<server name="CACHE_DRIVER" value="array"/>
<server name="MAIL_DRIVER" value="array"/>
<server name="QUEUE_CONNECTION" value="sync"/>
<server name="SESSION_DRIVER" value="array"/>
<server name="DB_DATABASE" value="test_homestead" />
But I am getting this error:
1) Tests\Feature\ViewArticleTest::user_can_view_an_article
Illuminate\Database\QueryException: SQLSTATE[HY000] [1049] Unknown database 'test_homestead' (SQL: SHOW FULL TABLES WHERE table_type = 'BASE TABLE')`
The error indicates that your test_homestead isn't available in your MySQL.
You should create a database by perform CREATE DATABASE test_homestead; in MySQL.
Or
Change the value in <server name="DB_DATABASE" value="test_homestead" /> to your desirable existing database name.
i am new in Laravel. Using local development environment with Homestead
Try to run simple test
namespace Tests\Feature;
use Tests\TestCase;
use Illuminate\Foundation\Testing\RefreshDatabase;
class UserTest extends TestCase
{
/**
* A basic test example.
*
* #return void
*/
public function testBasicTest()
{
$response = $this->get('/');
$response->assertStatus(200);
}
}
routes/web.php :
Route::get('/', function () {
return view('main');
});
Auth::routes();
Route::get('/home', 'HomeController#index')->name('home');
running phpunit returns 404 error
vagrant#homestead:~/code/laravel$ phpunit PHPUnit 6.4.3 by Sebastian
Bergmann and contributors.
.F. 3
/ 3 (100%)
Time: 1.07 seconds, Memory: 10.00MB
There was 1 failure:
1) Tests\Feature\UserTest::testBasicTest Expected status code 200 but
received 404. Failed asserting that false is true.
/home/vagrant/code/laravel/vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestResponse.php:78
/home/vagrant/code/laravel/tests/Feature/UserTest.php:25
I have tried to fix it with these ways
1.
Laravel phpunit always 404
updateTestCase.php
protected $baseUrl = 'http://localhost'
change with
protected $baseUrl = 'http://laravel.local'
2.
https://github.com/dingo/api/issues/540 and next to it
https://github.com/dingo/api/issues/571
use Illuminate\Foundation\Testing\WithoutMiddleware;
class BankTest extends TestCase {
use WithoutMiddleware;
Changing APP_URL in .env to
APP_URL=laravel.local
none of this helped
'laravel.local' works fine in browser
Please, help me fix it
I was running my application with following URL in browser.
http://localhost/app/public/
The default unit test having below line was failing. It was getting 404 response instead of 200.
$response = $this->get('/');
$response->assertStatus(200);
I changed APP_URL in .env file as below after reading above comments.
APP_URL=http://localhost
But I was still getting 404 error. After some trial and errors, I found that I needed to clear config cache.
php artisan config:cache
This did the trick and my test started working!!
I had the same problem, and if I run laravel with php artisan serve, it has to be:
APP_URL=http://127.0.0.1:8000/
The APP_URL, has to be exactly the URL of the website.
The website was working, but I didn't have that constant correctly, and PHPUnit was saying all time 404.
Don't forget to clear the cache, after change the config
php artisan config:cache
Have you tried with process isolation set to true in your phpunit.xml file? Our functional tests fail with 404 errors all over the place if we do not have process isolation:
<phpunit backupGlobals="false"
backupStaticAttributes="false"
bootstrap="bootstrap/autoload.php"
colors="true"
convertErrorsToExceptions="true"
convertNoticesToExceptions="true"
convertWarningsToExceptions="true"
processIsolation="true"
stopOnFailure="false">
For anyone having this problem, use APP_URL=http://localhost, this happens if you use vagrant I am not sure for other envs, still investigating.
Laravel tests run and expect environment variables. They expect variables like ENV_URL, ENV_KEY,... depending on your test case.
It is important that the ENV_URL variable is set to http://localhost disregarding your laravel/server setup. Tests work differently here.
Inside phpunit.xml, the line <server name="APP_ENV" value="testing"/> specifies which testing file to use. value="testing" expects a to use the .env.testing file, if it exists and fallbacks to .env.
There are two approaches that you can do from here on:
Approach A - Using .env.testing:
Create a copy of .env and name it .env.testing.
Verfiy that phpunit.xml includes the .env.testing file, like following <server name="APP_ENV" value="testing"/>
IMPORTANT Edit the .env.testing to use APP_URL=http://localhost as its URL. It doesn't matter under which URL you usually serve your application.
Edit other values to reflect your testing environment
Delete cache using php artisan cache:clear
Approach B - ENV values in phpunit.xml:
You can harcode all ENV values inside the phpunit.xml, like below
...
<php>
<server name="APP_URL" value="http://localhost"/>
<server name="APP_KEY" value="base64:e8+BZAzKrSR/LprdHQ2TfMaw+DOTWYmgpkFkEJHV+zw="/>
<server name="DB_CONNECTION" value="mysql"/>
<server name="DB_HOST" value="127.0.0.1"/>
<!-- More ENV values -->
...
<server name="BCRYPT_ROUNDS" value="4"/>
<server name="CACHE_DRIVER" value="array"/>
<!-- <server name="DB_CONNECTION" value="sqlite"/> -->
<!-- <server name="DB_DATABASE" value=":memory:"/> -->
<server name="MAIL_MAILER" value="array"/>
<server name="QUEUE_CONNECTION" value="sync"/>
<server name="SESSION_DRIVER" value="array"/>
<server name="TELESCOPE_ENABLED" value="false"/>
</php>
</phpunit>
Bonus - Hybrid Approach:
Use the main .env file and overwrite the APP_URL inside the phpunit.xml.
For this, there should not exist an .env.testing file or remove <server name="APP_ENV" value="testing"/> if it does exist.
...
<php>
<server name="APP_ENV" value="testing"/>
<!-- IMPORTANT - Overwrite the APP_URL -->
<server name="APP_URL" value="http://localhost"/>
<server name="BCRYPT_ROUNDS" value="4"/>
<server name="CACHE_DRIVER" value="array"/>
<!-- <server name="DB_CONNECTION" value="sqlite"/> -->
<!-- <server name="DB_DATABASE" value=":memory:"/> -->
<server name="MAIL_MAILER" value="array"/>
<server name="QUEUE_CONNECTION" value="sync"/>
<server name="SESSION_DRIVER" value="array"/>
<server name="TELESCOPE_ENABLED" value="false"/>
</php>
</phpunit>
The solution is to simply test using the url returned by
php artisan serve
as base url then run the tests
For example:
$response = $this->post('http://127.0.0.1:8001/api/register', [
'email' => '',
'phone' => '',
'password' => '',
'c_password' => '',
'role_id' => '',
]);
$response->assertStatus(401);
As #TooCooL mentioned, one could set APP_URL=http://localhost even if your project might be something as APP_URL=http://localhost/myproject.
Even better is to create another .env, it shall be called env.testing and there one can change APP_URL or even another database for testing purposes only and so on.
Phpunit will look for configuration at that file .env.testing
Although phpunit works fine even when APP_URL is set on my vhost name on my lamp stack.
Check out your /etc/hosts file as well.
Just for Laravel 8 devs.
Use full url inside get method
$response = $this->get('http://127.0.0.1:8000');
Leave APP_URL blank in .env file ie
APP_URL=
I have what I think is an uncommon issue but I'll try to explain as clear as I can. I have created a simple artisan command that does this
/**
* Execute the console command.
*/
public function handle()
{
$this->info("==> Cleaning up reports and docs...");
$command = new Process("rm -f tests/docs/* && rm -rf test/reports/*");
$command->run();
$this->warn("==> Reports and docs are clean");
$this->info("==> Executing Tests Suite...");
$command = new Process("vendor/bin/phpunit --coverage-html tests/reports --testdox-html tests/docs/reports.html -v --debug");
$command->run();
$this->info($command->getIncrementalOutput());
$this->warn("==> report generated >> test/reports. Documentation generated >> test/docs/reports.html");
}
This could seems kinda odd but it is actually pretty useful, it launch the PHPUnit with the coverage support and other stuff. The problem is that if I run this command like php artisan ludo237:full-test it will completely ignore the phpunit.xml in fact it will display and error saying that the MySQL database does not exists, even though I've set the sqlite connection inside my phpunit.xml speaking of which you can clearly see that is correct:
<?xml version="1.0" encoding="UTF-8"?>
<phpunit backupGlobals="false"
backupStaticAttributes="false"
bootstrap="bootstrap/autoload.php"
colors="true"
convertErrorsToExceptions="true"
convertNoticesToExceptions="true"
convertWarningsToExceptions="true"
processIsolation="false"
stopOnFailure="false">
<testsuites>
<testsuite name="Application Test Suite">
<directory suffix="Test.php">./tests</directory>
</testsuite>
</testsuites>
<filter>
<whitelist processUncoveredFilesFromWhitelist="true">
<directory suffix=".php">./app</directory>
</whitelist>
</filter>
<php>
<env name="APP_ENV" value="testing"/>
<env name="APP_DEBUG" value="true"/>
<env name="APP_URL" value="http://localhost:8000"/>
<env name="DB_CONNECTION" value="sqlite"/>
<env name="DB_DATABASE" value=":memory:" />
<env name="CACHE_DRIVER" value="array"/>
<env name="SESSION_DRIVER" value="array"/>
<env name="QUEUE_DRIVER" value="sync"/>
<env name="MAIL_DRIVER" value="log"/>
<env name="MAIL_PRETEND" value="true"/>
</php>
</phpunit>
I know that I can simply create a bash alias for that command line, in fact this is my current hot fix, but at this point I'm just curious to understand why when I launch the phpunit command from the artisan command it ignores the XML file.
Does anyone have a clue about this? Thank you!
It took me really a lot to debug this, but in the end I found why it is not working.
First of all, let me clarify that is nothing wrong with your code, even there is nothing wrong with the Process class, you will get the same behavior even by using native exec function.
Second, the phpunit.xml file is totally being read, no issues at all.
Said that, the real issue resides, on PHPUnit that doesn't allow you to re-define ( or override ) any env variable, because there is a check that prevents that.
This is because Laravel is not parsing the phpunit.xml file itself, and in the moment you're calling it, it's already too late and the environment variables are defined, either via putenv, $_SERVER and/or $_ENV.
Because of this, I created an Issue on PHPUnit, which even in latest versions ( as of today ), this issue persist, even if this was already asked in the past.
Unfortunately I have no solution yet for you, but let's cross our fingers and let's wait for PHPUnit to add the proposed force attribute :)
Best regards,
Julian
I have two different types of tests in my project - Acceptance and Unit tests and the problem is that CircleCi cant hit the database during the acceptance tests, though the .env variables are the same.
Here is the .env file:
DB_HOST=localhost
DB_DATABASE=db_testing
DB_USERNAME=homestead
DB_PASSWORD=secret
In PHPUnit.xml I have this:
<php>
<env name="APP_ENV" value="testing"/>
<env name="CACHE_DRIVER" value="array"/>
<env name="SESSION_DRIVER" value="array"/>
<env name="QUEUE_DRIVER" value="sync"/>
</php>
And in my app:
$app->loadEnvironmentFrom('.env.testing');
All this setup works on my local machine, but on circleci it complains that it cant reach the database. According to their docs, I don't need to create the database
If you use MySQL or Postgres, you can use the circle_test database and the ubuntu user rather than creating the database yourself. No password is required for any database.
Source: https://circleci.com/docs/manually/#databases
jdbc:postgresql://ubuntu:#127.0.0.1:5432/circle_test
Source: https://circleci.com/docs/configuration/#database
To use database provided by CircleCI, I think need to use:
# .env
DB_HOST=localhost
DB_DATABASE=circle_test
DB_USERNAME=ubuntu
DB_PASSWORD=