Update Test documentation about database behaviours

This update is based on what I have experienced and this conversation on Slack https://silverstripe-users.slack.com/archives/C6PLF83H9/p1571281365001600
This commit is contained in:
jeremy 2019-10-18 10:38:23 +11:00 committed by GitHub
parent 7873efde9c
commit 1197b94415
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -61,7 +61,7 @@ documentation.
## Test Databases and Fixtures ## Test Databases and Fixtures
SilverStripe tests create their own database when the test starts. New `ss_tmp` databases are created using the same SilverStripe tests create their own database when the test starts and fixture files are specified. New `ss_tmp` databases are created using the same
connection details you provide for the main website. The new `ss_tmp` database does not copy what is currently in your connection details you provide for the main website. The new `ss_tmp` database does not copy what is currently in your
application database. To provide seed data use a [Fixture](fixtures) file. application database. To provide seed data use a [Fixture](fixtures) file.
@ -71,7 +71,7 @@ permissions to create new databases on your server.
</div> </div>
<div class="notice" markdown="1"> <div class="notice" markdown="1">
The test database is rebuilt every time one of the test methods is run. Over time, you may have several hundred test The test database is rebuilt every time one of the test methods is run and cleaned up afterwards. If the test is interrupted the database is not cleaned up, over time, you may have several hundred test
databases on your machine. To get rid of them, run `sake dev/tasks/CleanupTestDatabasesTask`. databases on your machine. To get rid of them, run `sake dev/tasks/CleanupTestDatabasesTask`.
</div> </div>