Update lockfileVersion to *2*, but that's a side affect from npm
https://github.com/caolan/async/blob/master/CHANGELOG.md#v200
v2.0.0 allows importing functions modularily.
So I changed the code to only import the functions needed
instead of the whole thing.
* run prettier on script/test + replcae `==` with `===`
Fixes:
script\test.js:391 Expected '===' and instead saw '=='. (eqeqeq)
script\test.js:394 Expected '===' and instead saw '=='. (eqeqeq)
script\test.js:474 Expected '===' and instead saw '=='. (eqeqeq)
* remove excess spawn
The next line calls spawnTest
CONFIG.executableName depends on the ATOM_RELEASE_VERSION env variable
to work correctly on nightly releases.
Since this env variable is not being set for the testing steps, the
nightly release builds contain a wrong executableName on the testing
step, which causes a failure when trying to find the Atom executable.
This commit fixes that by stop using the executableName from the test
step, like it's done on other platforms.
This ensures that every test suite does not clutter subsequent ones. It
will also prevent altering the user's `~/.atom` directory when running
tests locally.
In these tests, we create a temporary `ATOM_HOME` to avoid cluttering
the user's real `~/.atom` folder.
Adding a symlink to the real `compile-cache` was introduced to speed up
main process tests, so that the transpilation cache could be reused.
Unfortunately, when the real `~/.atom` folder did not exist (such as on
a pristine environment on CI), it would confuse Atom, which would think
that it didn't need to re-create a `compile-cache` folder again, but
wouldn't be able to write to it because the symlink pointed to a
non-existant directory.
Main process tests were overhauled and made faster recently, so we can
safely remove this performance optimization.
For some reason, one main process test fails when run in a different
container than the one in which Atom was built. These tests are pretty
quick, so their impact on parallelism should be negligible.
