Changed to use different fixtures during testing

- this keeps production and test fixtures separate, so that changing the prod fixtures doesn't change the shape of our tests.
- we may still want to test that the production fixtures do what we expect, but that can be handled in a separate integration test, by specifically setting the fixture path

core/server/data/schema/fixtures/index.js

@@ -1,5 +1,8 @@
 const FixtureManager = require('./fixture-manager');
-const fixtures = require('./fixtures');
+const config = require('../../../../shared/config');
+
+const fixturePath = config.get('paths').fixtures;
+const fixtures = require(fixturePath);
 
 module.exports.FixtureManager = FixtureManager;
 module.exports.fixtureManager = new FixtureManager(fixtures);

core/shared/config/defaults.json

@@ -15,7 +15,8 @@
     "privacy": false,
     "useMinFiles": true,
     "paths": {
-        "contentPath": "content/"
+        "contentPath": "content/",
+        "fixtures": "core/server/data/schema/fixtures/fixtures"
     },
     "adapters": {
         "sso": {

core/shared/config/env/config.testing.json

@@ -49,5 +49,8 @@
         "useTinfoil": true,
         "useStructuredData": true
     },
-    "useMinFiles": false
+    "useMinFiles": false,
+    "paths": {
+        "fixtures": "test/utils/fixtures/fixtures"
+    }
 }

test/unit/shared/config/loader.test.js

@@ -95,6 +95,7 @@ describe('Config Loader', function () {
             //       and it doesn't make sure to check for "extra" keys
             Object.keys(pathConfig).should.eql([
                 'contentPath',
+                'fixtures',
                 'appRoot',
                 'corePath',
                 'clientAssets',