make option "testFileExtensions" accept an array like ['js','coffee']

If set "testFileExtensions": [ 'js', 'coffee']
in original code: this._nodeHasteTestRegExp is //__tests__/.*\.(js\|coffee)$/

This make Jest can't find tests: 0 Found 3 matching tests...

The change calls escapeStrForRegex() before join the string, so the gengerated regexp is:
//__tests__/.*\.(js|coffee)$/

Now Jest can find tests:
Found 3 matching tests...
remove tailing spaces
Fix # hrefs
Merge pull request #34 from ruanwz/patch-1

make option "testFileExtensions" accept an array like ['js','coffee']
Fix error where jasmine only reports results from first top-level suite

Previously we were assuming there was only one top-level test suite/describe().
As a result, we were only saving results from the *last* top-level suite we came
across :(

This fixes the issue to report all suites when multiple are present
0.1.11
Fewer max loops to speed up fake timer test

Previously the FakeTimer test took about 3 seconds on my computer; now it takes about 50 ms.
Merge pull request #33 from spicyj/faster-jest

Fewer max loops to speed up fake timer test
Merge pull request #41 from harshadsabne/harshadsabne-commits

Fix # hrefs
Dont cap error stack trace lines at nodes default of 10 for test errors
Remove default value for testPathIgnorePatterns in the React example and docs
Fix error where pretty-printing a frozen cyclic object fatals
Make window.location.host and location.hostname writable
Turns out we dont need to shim window.location.hostname or .host at all for jsdom!
Run jest with --harmony if it wasn't already doing so

Jest uses ES6 features in a couple of places. Right now I think it's just
WeakMaps but it would also be useful to test generators as well. ES6 is gated
behind the --harmony flag so we need to explicitly specify it when running jest.

The harmonize module tests to see if Node is currently running in ES6 mode. If
not, it spawns a Node child process with the same args and env as the parent but
with the --harmony flag.

Tested by running `./bin/jest.js -o` from a repo with some changes and didn't
get the crash that says: "Please run node with the --harmony flag!". (I got
another crash but that has to do with Haste).
Merge pull request #50 from ide/harmony

Run jest with --harmony if it wasn't already doing so
0.1.12
Start fake timers return token at > 0 to avoid accidental falseyness
Add a `config.globals` option for quickly specifying global variables that should be set in tests
Strip shebangs before pre-processing files