DevTools: Automagically detect user compiled content shell in npm test

DevTools: Automagically detect user compiled content shell in npm test

This should provide a seamless workflow if you're using:
* full chromium checkout - uses your compiled content shell (from out/Release)
if possible, otherwise it falls back to fetching a content shell from the cloud.
It will also compile devtools front-end so it can run tests in release mode.
* front-end github checkout - always uses a pre-compiled content shell fetched
from the cloud

This deprecates the run_inspector_tests.sh which will be replaced by "npm test".

I've also added documentation on `npm test` in the README.

BUG=654486
Committed: https://crrev.com/b57bb537043ed5d20edcc5f58c9a21575c03076b
Cr-Commit-Position: refs/heads/master@{#429076}

[chenwilliam, 2016-11-01 18:00:07]

Description was changed from

==========
DevTools: Automagically detect user compiled content shell in npm test

This should provide a seamless workflow if you're using:
* full chromium checkout - uses your compiled content shell (from out/Release)
if possible, otherwise it falls back to fetching a content shell from the cloud
* front-end github checkout - always uses a pre-compiled content shell fetched
from the cloud

I've also added documentation on `npm test` in the README.

BUG=654486
==========

to

==========
DevTools: Automagically detect user compiled content shell in npm test

This should provide a seamless workflow if you're using:
* full chromium checkout - uses your compiled content shell (from out/Release)
if possible, otherwise it falls back to fetching a content shell from the cloud.
It will also compile devtools front-end so it can run tests in release mode.
* front-end github checkout - always uses a pre-compiled content shell fetched
from the cloud

This deprecates the run_inspector_tests.sh which will be replaced by "npm test".

I've also added documentation on `npm test` in the README.

BUG=654486
==========

[chenwilliam, 2016-11-01 18:00:07]

chenwilliam@chromium.org changed reviewers:
+ dgozman@chromium.org

[chenwilliam, 2016-11-01 18:00:57]

PTAL.

[dgozman, 2016-11-01 18:46:21]

lgtm

[chenwilliam, 2016-11-01 18:47:52]

The CQ bit was checked by chenwilliam@chromium.org

[commit-bot: I haz the power, 2016-11-01 18:48:13]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-01 19:47:21]

Description was changed from

==========
DevTools: Automagically detect user compiled content shell in npm test

This should provide a seamless workflow if you're using:
* full chromium checkout - uses your compiled content shell (from out/Release)
if possible, otherwise it falls back to fetching a content shell from the cloud.
It will also compile devtools front-end so it can run tests in release mode.
* front-end github checkout - always uses a pre-compiled content shell fetched
from the cloud

This deprecates the run_inspector_tests.sh which will be replaced by "npm test".

I've also added documentation on `npm test` in the README.

BUG=654486
==========

to

==========
DevTools: Automagically detect user compiled content shell in npm test

This should provide a seamless workflow if you're using:
* full chromium checkout - uses your compiled content shell (from out/Release)
if possible, otherwise it falls back to fetching a content shell from the cloud.
It will also compile devtools front-end so it can run tests in release mode.
* front-end github checkout - always uses a pre-compiled content shell fetched
from the cloud

This deprecates the run_inspector_tests.sh which will be replaced by "npm test".

I've also added documentation on `npm test` in the README.

BUG=654486
==========

[commit-bot: I haz the power, 2016-11-01 19:47:21]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-11-01 19:57:38]

Description was changed from

==========
DevTools: Automagically detect user compiled content shell in npm test

This should provide a seamless workflow if you're using:
* full chromium checkout - uses your compiled content shell (from out/Release)
if possible, otherwise it falls back to fetching a content shell from the cloud.
It will also compile devtools front-end so it can run tests in release mode.
* front-end github checkout - always uses a pre-compiled content shell fetched
from the cloud

This deprecates the run_inspector_tests.sh which will be replaced by "npm test".

I've also added documentation on `npm test` in the README.

BUG=654486
==========

to

==========
DevTools: Automagically detect user compiled content shell in npm test

This should provide a seamless workflow if you're using:
* full chromium checkout - uses your compiled content shell (from out/Release)
if possible, otherwise it falls back to fetching a content shell from the cloud.
It will also compile devtools front-end so it can run tests in release mode.
* front-end github checkout - always uses a pre-compiled content shell fetched
from the cloud

This deprecates the run_inspector_tests.sh which will be replaced by "npm test".

I've also added documentation on `npm test` in the README.

BUG=654486

Committed: https://crrev.com/b57bb537043ed5d20edcc5f58c9a21575c03076b
Cr-Commit-Position: refs/heads/master@{#429076}
==========

[commit-bot: I haz the power, 2016-11-01 19:57:39]

Patchset 4 (id:??) landed as
https://crrev.com/b57bb537043ed5d20edcc5f58c9a21575c03076b
Cr-Commit-Position: refs/heads/master@{#429076}