Closed Bug 1169775 Opened 9 years ago Closed 9 years ago

[Raptor] Refactor mozdevice and Raptor to take advantage of Marionette

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
FxOS-S3 (24Jul)

People

(Reporter: Eli, Assigned: Eli)

References

Details

(Whiteboard: [systemsfe])

Just like the title says. The goal here is to try and move away from using Orangutan to trigger interactions so we have a higher-level interface to work with. Important to note is the syntax for these tests should remain similar to the current structure of Raptor tests. TLDR; we need the Marionette bits without the Mocha bits.

Raptor and mozdevice will still get its performance data from logcat. We hopefully will no longer need a `make raptor` step since these libs are now in the Gaia tree, and should be able to get away from the homescreens.json configuration.
Depends on: 1169788
Whiteboard: [systemsfe]
Target Milestone: --- → 2.2 S14 (12june)
Blocks: 1159153
Eli, is there a new deadline for implementing this? Thanks a lot!
Flags: needinfo?(eperelman)
This task does not have a well-defined deadline, was hoping to finish it this quarter, but that is not set in stone.
Flags: needinfo?(eperelman)
Blocks: 1169584
No longer blocks: nga-apps-contacts
Blocks: 1169116
Summary: [Raptor] Refactor mozdevice and Raptor to take advantage of in-tree Marionette → [Raptor] Refactor mozdevice and Raptor to take advantage of Marionette
Hei Eli,

do you have any update on this?

The contacts team is moving fast and we have separation for views and activities, and will be really good to try that the work that we are doing is not adding more regressions.

Still on your radar? Any ETA?
Flags: needinfo?(eperelman)
Hey Francisco! Yep, it's in review right now [1][2]. If you are interested in beta testing the new tool, ping me in the #raptor room.

[1] https://github.com/eliperelman/mozilla-raptor/pull/1
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1169788#c1
Flags: needinfo?(eperelman)
That's great!

Looking forward for using it. Some people working on porting the apps to the new architecture will be working together the first week in August to try to speed up the process.

We are planning to use a big monitor with raptor to check how are we doing with our commits. So yes, we will  be testing it soon!
This has landed, with the caveat that we are still waiting on a PR to enable automatic adb forwarding. I'll have updated docs soon. Anyone with questions can ping me in the #raptor room.

In master: https://github.com/eliperelman/mozilla-raptor/commit/3d6a772f7ea4b5950dd4c8ac3e5be8832967f554
In npm: @mozilla/raptor v1.0.0
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: 2.2 S14 (12june) → FxOS-S3 (24Jul)
You need to log in before you can comment on or make changes to this bug.