Open Bug 1504472 Opened 6 years ago Updated 5 years ago

testview UI suggestions

Categories

(Tree Management :: Push Health, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: mozbugz, Unassigned)

Details

Sorry for the "fluffy" bug, I'm trying to gather thoughts about how testview could help me (and hopefully others) better. Feel free to split as needed. I've recently wanted to use testview to try and find potential issues in a patch, but it proved difficult to sort through all failures -- some expected, some unrelated, and maybe some relevant needles in this haystack. E.g., this try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=bff3eb8054238330eae8305765d73e5cdbf7d2ff produced this testview: https://treeherder.mozilla.org/testview.html?repo=try&revision=bff3eb8054238330eae8305765d73e5cdbf7d2ff There are lots of failures because as part of my try I enabled the profiler everywhere. By default, testview groups results by test names and collapses results. There is a filter but it only applies to test names. Here are some things I would have liked to be able to do: - Expand all (so I can do a manual text-search, or copy-paste elsewhere). - Filter by something in the test results (e.g., "setSleeping", as I expected a crash there if my patch was wrong). - Filter *out* results I don't care about (e.g., "fixBaselineReturnAddress", which was caused by the profiler running at the wrong time, but was not part of my main patch of interest). - Index by unique test results and sort by counts. - Filter out results which have an associated bug number. - Export to a spreadsheet-friendly format, so I can do my own processing. Or json if that's easier for you; or whatever format all this juicy data is in. I imagine some suggestion are much more complex than others. So anything simple first would be really nice to have, especially export suggestions so we can get quick access to the raw data -- so you don't spend time implementing pretty UI things that only few people may use. TIA!
Priority: -- → P3

These are some nice suggestions. Some of them apply to Push Health, the successor to Test-View

Component: Treeherder: Test-based View → Push Health
You need to log in before you can comment on or make changes to this bug.