Page MenuHomePhabricator

Add synthetic testing for editing process (save timing)
Open, HighPublic

Description

Today we only measure save timing with RUM metrics, it would be helpful to also do synthetic.

Event Timeline

Peter created this task.Jan 23 2019, 7:29 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 23 2019, 7:29 AM
Peter moved this task from Inbox to Doing on the Performance-Team board.Jan 30 2019, 2:52 PM
Peter added a subscriber: Krinkle.Jan 30 2019, 2:56 PM

Had a go today and I could go through the full flow. Now we just need to decide what to measure :)

We probably want to get the metrics that we send to statsv. I'll ping you @Krinkle the coming days.

Krinkle renamed this task from Try measuring save timings with synthetic testing to Add synthetic testing for editing (save timing).Jun 6 2019, 10:31 AM
Krinkle renamed this task from Add synthetic testing for editing (save timing) to Add synthetic testing for editing process (save timing).
Krinkle triaged this task as High priority.
Peter added a comment.Thu, Oct 10, 9:29 AM

I've started this again, trying to make a more sane script that works. I can go through the full scenario on beta and we need to find a way to get the important metric(s).

@Krinkle is it anything more than ve.mwTarget.performance.user.saveCompletewe need? What do you think is the best way forward so we can make it available in JavaScript so we easy can get that?

Probably easiest to capture via mw.trackSubscribe. although that will be asynchronous.