Closed
Bug 1210415
Opened 10 years ago
Closed 9 years ago
Make TelemetryController.reset() trigger all the Telemetry shutdown/setup routines
Categories
(Toolkit :: Telemetry, defect, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
DUPLICATE
of bug 1145188
| Tracking | Status | |
|---|---|---|
| firefox44 | --- | affected |
People
(Reporter: Dexter, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [unifiedTelemetry] [measurement:client])
In Telemetry tests, we're often required to simulate a product restart by calling the |.reset| method of the sub module we'd like to test (e.g. TelemetrySend).
We should change TelemetryController.reset so that it correctly triggers the proper shutdown/setup procedures in itself and the other modules, to correctly mimic a product restart.
|
||
Updated•10 years ago
|
Points: --- → 2
Priority: -- → P3
Summary: Make TelemetryController.reset() trigger all the Telemetry shutdown/setup routines → Telemetry redesign: Make TelemetryController.reset() trigger all the Telemetry shutdown/setup routines
Whiteboard: [unifiedTelemetry][measurement:client] → [unifiedTelemetry] [measurement:client]
|
|
||
Updated•10 years ago
|
Summary: Telemetry redesign: Make TelemetryController.reset() trigger all the Telemetry shutdown/setup routines → Make TelemetryController.reset() trigger all the Telemetry shutdown/setup routines
|
Reporter | |
Comment 1•9 years ago
|
||
In bug 1145188 we made TelemetryController.setup also trigger TelemetrySession's initialization.
We should reflect this change in the tests by consolidating the calls to the setup functions: if both TelemetryController.setup() and TelemetrySession.setup() are called in a test, we should just keep the former.
|
|
Reporter | |
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•