Another way to do Laravel database testing (SQLite)

This article mainly introduces another method to conduct Laravel database testing (SQLite), which has certain reference value. Now I share it with you. Friends in need can refer to it

Laravel database Testing

In terms of testing, Laravelbuilt-in usePHPUnit provides a very convenient solution. For the test of database addition, deletion, modification and query, a very important problem to be solved is how to restore the original appearance of the database after the test is completed. For example, to test a user registration method, a user record needs to be inserted into the database, but after the test is completed, , we don’t want this test case to be saved in the database. In order to solve this problem, Laravel provides a very convenient solution:

• Use migrations: DatabaseMigrations

• Use transactions: DatabaseTransactions

Reference: https://laravel.com/docs/5.3/database-testing#resetting-the-database- after-each-test

Another solution: use the in-memory database of SQLite:memory:

Laravel The two solutions provided still perform read and write operations on the database. Sometimes you may not want to do this (for example, multiple people share an online development database). In this case, you can also use a more elegant way: SQLlite, the logic is actually very simple: when running the test case, replace the database connection with SQLite.

Usage Example

For example, we have the following test class (this example is not representative, it is only used to illustrate the problem, and it is assumed that SQLite has been installed on this machine):

class HomePageTest extends TestCase {
    
    public function testHomePage() 
    {
        // 创建一个测试用户，并保存
        $user = factory(App\User::class)->create();
        $this->actingAs($user)->visit('/home')->see('Dashboard');
    }
}

• First add it in the Laravel database configuration file, that is, the connections array of config/database.php A new database connection

'sqlite' => [
    'driver' => 'sqlite',
    'database' => ':memory:',
    'prefix' => '',
],

A very important parameter here is'database' => ':memory:',:memory:The database is an in-memory database built into SQLite. Each time a test case is run, a new database will be created in the memory and will be automatically cleared after the test is completed and the database connection is closed. It has good performance. Isolation, and because it is in memory, it is also very fast. These features are very convenient for testing. This is also a very important reason why we choose the SQLite database as the test library. For a detailed explanation, click here.

• Then you need to modify the configuration file of PHPUnit. In phpunit.xml, change the database connection to the SQLite just defined Connection

<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"/>
    
    <!-- 将数据库连接改为刚刚定义的SQLite连接 -->
    <env name="DB_CONNECTION" value="sqlite" />
</php>

This overrides the database connection DB_CONNECTION=mysql defined in .env and tells the framework to run the test Sometimes, use sqlite connection instead of mysql connection.

• Finally, you need to perform database migration before running the test case, and add the setUp method to the base class of the test class, which is TestCase.php

public function setUp()
{
    parent::setUp();
    // 执行数据库迁移 
    $this->artisan('migrate');
}

In this way, before each test case is executed, all migrations will be performed to the :memory: database of SQLite to generate business Data table required for logic.

Advantages and Disadvantages of the Solution

• The key point of this solution is to use a built-in memory database SQLite:memory:, so It is relatively fast, has good isolation, and will not have any impact on our development database.

• Of course, this solution also has shortcomings. If the project database is huge, there are a large number of data tables or migration files, it will consume a lot of memory. When running the test, there may be insufficient memory, resulting in Test interrupted. At this time, you need to allocate appropriate memory to PHP and modify the configuration in php.inimemory_limit = 128M

The above is the entire content of this article , I hope it will be helpful to everyone’s learning. For more related content, please pay attention to the PHP Chinese website!

Related recommendations:

<a title="如何解决Laravel.log 文件写入的问题" href="http://www.php.cn/php-weizijiaocheng-406465.html" target="_blank">How to solve the problem of writing the Laravel.log file</a>

Laravel development environment deployment Homestead installation and configuration process (windows system)

Laravel routing (router) graphic and text explanation

The above is the detailed content of Another way to do Laravel database testing (SQLite). For more information, please follow other related articles on the PHP Chinese website!