From 7812f34a2d583db171c7b8cb52aa3afe768ea945 Mon Sep 17 00:00:00 2001 From: Andrew Aitken-Fincham Date: Tue, 4 Jul 2017 12:50:57 +0100 Subject: [PATCH] remove info div to fix formatting --- docs/en/02_Developer_Guides/06_Testing/04_Fixtures.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/en/02_Developer_Guides/06_Testing/04_Fixtures.md b/docs/en/02_Developer_Guides/06_Testing/04_Fixtures.md index cfc8f6004..1351a1c6a 100644 --- a/docs/en/02_Developer_Guides/06_Testing/04_Fixtures.md +++ b/docs/en/02_Developer_Guides/06_Testing/04_Fixtures.md @@ -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 fixtures - all we have to do is define them. -
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 { - protected static $fixture_file = [ + protected static $fixture_file = array( 'fixtures.yml', 'otherfixtures.yml' - ]; + ); } -
- 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