Open Bug 1736351 Opened 4 years ago Updated 3 years ago

Add tests to website sample and run them on CI

Categories

(Data Platform and Tools :: Glean: SDK, task, P4)

task

Tracking

(Not tracked)

REOPENED

People

(Reporter: brizental, Unassigned)

Details

(Whiteboard: [glean-sdk:backlog][glean-js])

No description provided.
Priority: P4 → P3
Whiteboard: [telemetry:glean-js:m?]
Priority: P3 → P2
Assignee: nobody → brizental
Priority: P2 → P1
Assignee: brizental → nobody
Priority: P1 → P2
Priority: P2 → P4
Whiteboard: [telemetry:glean-js:backlog]

Although not really in the website sample, we now have a suite of tests running for Glean.js on websites on Browserstack after each merge, which I feel like cover this necessity well enough at least for now.

See: https://github.com/mozilla/glean.js/pull/1136

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX

Re-opening this because I changed my mind. The smoke tests are kind of hacky and it would be nice to have proper tests in the sample 1. because users can rely on them as examples 2. it's an opportunity to figure out how to write non-hacky tests for websites.

Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Component: Glean.js → Glean: SDK
Whiteboard: [telemetry:glean-js:backlog] → [glean-sdk:backlog][glean-js]
You need to log in before you can comment on or make changes to this bug.