The `test` command fails with multiple arguments when given a unary operator such as '-e'. Add a function that can test one or more files by looping over all files.

* E2E: run tests when react is ready

* Entangle e2e with callbacks

* Remove unused e2e lines

* Use a more sophisticated template for end-to-end testing.

* Not publish integration tests to npm

* Use "commander" for  cli argv handling

* Handle different scripts version forms and exits without a name given

* Prepare the commands for testing with a template

* Fix dev "template" path

* Add various features to test

* Test various features separately

* Test language features

* Comment unused e2e.sh lines

* Add "development" tests

* Test environment variables

* Test webpack plugins

* Replace kitchensink README

* Switch integration tests from jest to mocha

* Use `fs-extra`

* Use the correct folders

* Do some cleanup

* Print a better message for `--template`

* Test `npm start` with and without https

* Separate fast e2e testing from kitchensink testing

* Hide `--internal-testing-template` (former `--template`) CLI option

* gh-1269: Enabling nested folder paths for project name

* gh-1269: Added "fs-extra" and removed "path-exists"

* gh-1269: Added e2e test cases to verify nested folder names

* Tweak minimal Node error message

* Tweak console messages

* It doesn't need to be from npm

* Try to fix e2e test

* Use "commander" for  cli argv handling

* Handle different scripts version forms and exits without a name given

* Revert comment about min supported node version

* Check sooner for the minimal node version

* Add travis test for node <4

* Parse stderr in node versions <4

* Remove bundledDependencies
* Change the e2e scripts to use local file dependencies instead of
  bundledDependencies to test the packages

Loads all files not already handled by other loaders.
Also, switch image loading from file loader to url-loader.

In the `create-react-app` command, try to install packages using Yarn.
If Yarn is not installed, use npm instead.

In `react-scripts`, detect if the project is using Yarn by checking if
a `yarn.lock` file exists. If the project is using Yarn, display all
the instructions with Yarn commands and use Yarn to install packages
in `init` and `eject` scripts.

* Clean up e2e script

* Link to local packages after ejecting

Only copy our own packages to bundledDependencies in the e2e test

* Fix the e2e test

In the end-to-end test, we want to test all the latest packages from
the monorepo instead of the versions from npm.

To do this we will now:
* run `lerna bootstrap` in the repo root folder before packaging react-scripts
* bundle the deps like we do for releases, so the e2e test uses those packages

* Fix copy-pasted comment

tagging dev-only code (@remove-on-publish-begin/end) and pre-eject-only code (@remove-on-eject-begin/end) #257 (#257)

Fixes #532

* Update Jest

* Remove default snapshot test

* Fix a few things

* Add a simple default test

* App.spec.js -> App.test.js

* Fix e2e test

* Bump Jest

* Load favicon through html-loader.

Fixes #291.

* Add test for *.ico in e2e test suite

* Configure html-loader to process <link href="...">

* Address feedback on html-loader inclusion.

* Place favicon.ico at the root of the build dir

* Make comment style consistent between prod and dev webpack configs

* Fix html-loader config in dev mode

* Use /static paths for assets

* Fix e2e test

I think this should solve #258

* Improve error handling in E2E script

* Expose e2e.sh as npm test script

* dogfood eslint config

* moved linting to e2e