Closed
Bug 1169230
Opened 9 years ago
Closed 2 months ago
Write basic tests for crash report submitting from the crash reporter client
Categories
(Toolkit :: Crash Reporting, defect)
Toolkit
Crash Reporting
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox41 | --- | affected |
People
(Reporter: ted, Unassigned)
References
Details
In bug 1166759 I fixed a bug where the Mac crashreporter client failed to submit reports if the annotation data was not valid UTF-8. Unfortunately we don't have any tests that the crash reporter client can actually submit reports, so we don't have an automated test for this. This probably needs bug 379290 fixed in order to avoid involving GUI automation of native widgets on multiple platforms as part of the test. I'm not really sure where we'd stick this kind of test, maybe a Marionette test would work? We'd need to be able to crash the browser, have the crash reporter client run and submit a report (to a python httpd, presumably), and verify that we got the data we expected.
Updated•2 years ago
|
Severity: normal → S3
Comment 1•2 months ago
|
||
The new crash reporter client has many tests of submission and edge cases.
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•