Closed Bug 1509036 Opened 6 years ago Closed 6 years ago

Write a proposal for testing consumers/user metrics in glean

Categories

(Toolkit :: Telemetry, enhancement, P1)

Product:
Toolkit
Component:
Telemetry
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox65 --- affected

People

(Reporter: Dexter, Assigned: travis_)

References

Details

(Whiteboard: [telemetry:mobilesdk:m5])

Right now, we have no easy way to test if some application is correctly accumulating data in metrics other than creating a stub HTTP server, passing its address via `Config()`, triggering the pings and then parsing the result. We should probably think of a better way to do this.
Blocks: 1491345
Priority: -- → P3
Whiteboard: [telemetry:mobilesdk:m?]
Whiteboard: [telemetry:mobilesdk:m?] → [telemetry:mobilesdk:m4]
Assignee: nobody → tlong
Priority: P3 → P1

Work in progress proposal

Link to notes from meeting with Severin regarding test requirements and current testing usages: notes

I've updated the proposal to show the latest feedback.

To summarize, I don't think anything we are currently doing blocks using hamcrest matchers or OkHttp interceptors. What I would like to do is create a test wrapper or extension of the glean public API to expose metric values for test to interface with for the purpose of validating stored data.

What I'm still not clear on is if the assertions and intercepting of network traffic should be done internal to the test API, or if this is something that a consuming app should do since testing requirements may be different from one app to another. I tend to lean towards the direction that it should be the responsibility of the consuming application to perform the validation because the needs of the specific app may differ.

Please take a look and let me know if I need to add more details or if you have any additional feedback.
Proposal

Summary: Provide a way to test consumers/user metrics in glean → Write a proposal for testing consumers/user metrics in glean
Whiteboard: [telemetry:mobilesdk:m4] → [telemetry:mobilesdk:m5]

Proposal finalized, moving to implementation: Bug 1522125

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.