3.4.0 Add Fixtures for Easier Compares

Author: devloco

packages/react-scripts/fixtures/kitchensink/package.json

@@ -0,0 +1,5 @@
+{
+  "name": "kitchensink",
+  "main": "template.json",
+  "version": "1.0.0"
+}

packages/react-scripts/fixtures/kitchensink/template.json

@@ -0,0 +1,12 @@
+{
+  "package": {
+    "dependencies": {
+      "bootstrap": "4.3.1",
+      "jest": "24.9.0",
+      "node-sass": "4.12.0",
+      "normalize.css": "7.0.0",
+      "prop-types": "15.7.2",
+      "test-integrity": "2.0.1"
+    }
+  }
+}

packages/react-scripts/fixtures/kitchensink/template/.env

@@ -0,0 +1,7 @@
+REACT_APP_X = x-from-original-env	
+REACT_APP_ORIGINAL_1 = from-original-env-1	
+REACT_APP_ORIGINAL_2 = from-original-env-2	
+REACT_APP_BASIC = basic	
+REACT_APP_BASIC_EXPAND = ${REACT_APP_BASIC}	
+REACT_APP_BASIC_EXPAND_SIMPLE = $REACT_APP_BASIC	
+REACT_APP_EXPAND_EXISTING = $REACT_APP_SHELL_ENV_MESSAGE

packages/react-scripts/fixtures/kitchensink/template/.env.development

@@ -0,0 +1,2 @@
+REACT_APP_X = x-from-development-env
+REACT_APP_DEVELOPMENT = development

packages/react-scripts/fixtures/kitchensink/template/.env.local

@@ -0,0 +1,2 @@
+REACT_APP_X = x-from-original-local-env
+REACT_APP_ORIGINAL_2 = override-from-original-local-env-2

packages/react-scripts/fixtures/kitchensink/template/.env.production

@@ -0,0 +1,2 @@
+REACT_APP_X = x-from-production-env
+REACT_APP_PRODUCTION = production

packages/react-scripts/fixtures/kitchensink/template/.flowconfig

@@ -0,0 +1,8 @@
+[ignore]
+<PROJECT_ROOT>/node_modules/fbjs/.*
+
+[include]
+
+[libs]
+
+[options]

packages/react-scripts/fixtures/kitchensink/template/README.md

@@ -0,0 +1,52 @@
+# Contributing to Create React App's E2E tests
+
+This is an end to end kitchensink test suite, but has multiple usages in it.
+
+## Running the test suite
+
+Tests are automatically run by the CI tools.
+In order to run them locally, without having to manually install and configure everything, the `yarn e2e:docker` CLI command can be used.
+
+This is a script that runs a **Docker** container, where the node version, git branch to clone, test suite, and whether to run it with `yarn` or `npm` can be chosen.
+Run `yarn e2e:docker --help` to get additional info.
+
+If you need guidance installing **Docker**, you should follow their [official docs](https://docs.docker.com/engine/installation/).
+
+## Writing tests
+
+Each time a new feature is added, it is advised to add at least one test covering it.
+
+Features are categorized by their scope:
+
+- _env_, all those which deal with environment variables (e.g. `NODE_PATH`)
+
+- _syntax_, all those which showcase a single EcmaScript syntax feature that is expected to be transpiled by **Babel**
+
+- _webpack_, all those which make use of webpack settings, loaders or plugins
+
+### Using it as Unit Tests
+
+In it's most basic for this serve as a collection of unit tests on a single functionality.
+
+Unit tests are written in a `src/features/**/*.test.js` file located in the same folder as the feature they test, and usually consist of a `ReactDOM.render` call.
+
+These tests are run by **jest** and the environment is `test`, so that it resembles how a **Create React App** application is tested.
+
+### Using it as Integration Tests
+
+This suite tests how the single features as before behave while development and in production.
+A local HTTP server is started, then every single feature is loaded, one by one, to be tested.
+
+Test are written in `integration/{env|syntax|webpack}.test.js`, depending on their scope.
+
+For every test case added there is only a little chore to do:
+
+- a `case` statement must be added in `src/App.js`, which performs a dynamic `import()` of the feature
+
+- add a test case in the appropriate integration test file, which calls and awaits `initDOM` with the previous `SwitchCase` string
+
+A usual flow for the test itself is something similar to:
+
+- add an `id` attribute in a target HTML tag in the feature itself
+
+- since `initDOM` returns a `Document` element, the previous `id` attribute is used to target the feature's DOM and `expect` accordingly

packages/react-scripts/fixtures/kitchensink/template/gitignore

@@ -0,0 +1,15 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+
+# dependencies
+node_modules
+
+# testing
+coverage
+
+# production
+build
+
+# misc
+.DS_Store
+.env
+npm-debug.log

packages/react-scripts/fixtures/kitchensink/template/integration/config.test.js

@@ -0,0 +1,25 @@
+/**
+ * Copyright (c) 2015-present, Facebook, Inc.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
+import initDOM from './initDOM';
+
+describe('Integration', () => {
+  describe('jsconfig.json/tsconfig.json', () => {
+    let doc;
+
+    afterEach(() => {
+      doc && doc.defaultView.close();
+      doc = undefined;
+    });
+
+    it('Supports setting baseUrl to src', async () => {
+      doc = await initDOM('base-url');
+
+      expect(doc.getElementById('feature-base-url').childElementCount).toBe(4);
+    });
+  });
+});