Closed Bug 1185984 Opened 9 years ago Closed 2 years ago

Split desktop_unittest.py into per-harness scripts

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INACTIVE

People

(Reporter: jgraham, Assigned: gbrown)

Details

desktop_unittest.py is rather complex, and it seems like a large amount of this complexity comes from sharing a single frontend to multiple harnesses, which necessitates a complex configuration format and inline if-blocks to handle cases that are nevertheless too complex. Replacing this with simpler per-harness script files and code sharing via inheritance/composition rather than configuration would be a win for maintainability.
+1
+1

this is overdue for a cleanup.

It was my first intern project and was designed for mochitest, reftest, and xpcshell. It has obviously not scaled well, particularly the way we have so many edge cases now: in-tree configs, suite specific tests.zip extraction, log parsing, unique platform  behaviour for special suites that act like mochitest but are not.
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.