Open
Bug 1882360
Opened 2 years ago
Updated 2 years ago
Update documentation with information on perftest workflow/planning/FAQ
Categories
(Testing :: Performance, enhancement, P3)
Testing
Performance
Tracking
(Not tracked)
ASSIGNED
People
(Reporter: kshampur, Assigned: kshampur)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxp])
We (perftest) have had a different planning approach since ~Oct 2023. So far things have been going smooth and it would be worthwhile to update our documentation for further visibility to the org
brainstorm of things to cover (not exhaustive.
- Outline of current workflow in contrast to what we were doing before
- Operational/vision tasks, importance of prioritizing intermittents/permas & operational
- Within operational: how do we rank tasks? e.g. OKR ~perma failures ~ high frequency intermittents > everything else (but also case by case)
- Blockers we have
- Things outside of our control (e.g. CI stuff )
- Why is task X not running yet? Taking so long in queue? What can someone do about it?
- Requesting new devices? Associated costs, people to talk to, etc.
- Why things like mach try perf have a limit on task size
etc...
We could also do a follow up blog post highlighting some of this at a higher level.
| Assignee | ||
Updated•2 years ago
|
Whiteboard: [fxp]
Updated•2 years ago
|
Updated•2 years ago
|
Summary: Update documentation with information on perfrest workflow/planning/FAQ → Update documentation with information on perftest workflow/planning/FAQ
Updated•2 years ago
|
Blocks: perftest-docs
You need to log in
before you can comment on or make changes to this bug.
Description
•