tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #7126 from andrewandante/patch-1

Browse Source 
FIX remove info div to fix formatting
This commit is contained in:
Daniel Hensby 2017-07-04 13:46:18 +01:00 committed by GitHub
commit c472957bd2
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/en/02_Developer_Guides/06_Testing/04_Fixtures.md
View File

@ -9,7 +9,6 @@ SilverStripe starts with a fresh database containing no records. `Fixtures` prov
to load into the database. The [api:SapphireTest] class takes care of populating a test database with data from to load into the database. The [api:SapphireTest] class takes care of populating a test database with data from
fixtures - all we have to do is define them. fixtures - all we have to do is define them.
<div class="info" markdown='1'>
To include your fixture file in your tests, you should define it as your `$fixture_file`: To include your fixture file in your tests, you should define it as your `$fixture_file`:
@ -34,15 +33,13 @@ You can also use an array of fixture files, if you want to use parts of multiple
class MyNewTest extends SapphireTest { class MyNewTest extends SapphireTest {
protected static $fixture_file = [ protected static $fixture_file = array(
'fixtures.yml', 'fixtures.yml',
'otherfixtures.yml' 'otherfixtures.yml'
]; );
} }
</div>
Typically, you'd have a separate fixture file for each class you are testing - although overlap between tests is common. Typically, you'd have a separate fixture file for each class you are testing - although overlap between tests is common.
Fixtures are defined in `YAML`. `YAML` is a markup language which is deliberately simple and easy to read, so it is Fixtures are defined in `YAML`. `YAML` is a markup language which is deliberately simple and easy to read, so it is