1143363 - [Raptor] Investigate further decoupling of Gaia from Raptor

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)

Description

[:Eli Perelman]

At the moment the only thing Raptor really relies on Gaia for is profile creation. While the actual tests exist in Gaia, there is no real reason they are there other than tradition. Because the tests live in Gaia, every time a release to Raptor is created, we are forced to bump the package in Gaia, which doesn't actually do anything other than create overhead.

I would like to experiment with decoupling Raptor from Gaia with some goals in mind:

* Speed up Raptor integration/development/releasing by removing the gaia-raptor package from Gaia
* Convert Raptor into an npm global package which can be addressed via `raptor` in the command line. Globally installing Raptor gives us the power to potentially run it from any directory.
* Decrease reliance on environment variables.
* Move the tests into the Raptor repo. This will allow us to do something like `APP=clock raptor test coldlaunch`. This will save developers from having to memorize test paths and put the power back into the repo for test definitions.
* Support performance testing of any app, not just the ones defined in Gaia's apps/. I'm not yet sure how to accomplish this, whether it's with different custom homescreens, or different coordinate caching systems, etc, but I would like to performance test any app on the device, even 3rd party apps.

Comment 1

[:Eli Perelman]

I think it's possible to make some changes to Raptor to support running it against 3rd-party application, but it takes a *deeper* coupling to Gaia to make it better, which is not what I expected. I will be moving gaia-raptor and possible mozdevice into the Gaia tree.