Closed Bug 1031255 Opened 10 years ago Closed 7 years ago

Handle WebSocket disconnects by logging test results as errors instead of raising

Categories

(Firefox OS Graveyard :: Certification Suite, defect)

Product:
Firefox OS Graveyard
Component:
Certification Suite
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: ato, Unassigned)

Details

We are currently raising an exception when the client WebSocket closes abruptly for whatever reason.  This causes us to loose test results because the remaining tests aren't recorded.

Instead we should handle the disconnect and have the remaining tests reported as errors.
Assignee: nobody → ato
Assignee: ato → nobody
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.