Possible smoke test suggestions for dev/contributors

RESOLVED FIXED

Status

Tree Management
Treeherder: Docs & Development
P5
enhancement
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: jfrench, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

3 years ago
It crossed my mind, it might be handy to have a simple, very small list of key functionality to run through (or if we get fancy later some automated equivalent) to test a local instance of treeherder before opening PR's.

For example testing pinning, repo switching, filters, etc, or whatever has historically proven fragile.

We might want one for people who are staff and have full functionality access, or a subset which works for anyone.

We could possibly post this bullet point list on the Wiki as a link in the Contributing section. Not that it would be mandatory, but it may help encourage that mindset during development and prior to commits.

Updated

3 years ago
Blocks: 1072681

Updated

3 years ago
No longer blocks: 1072681
Component: Treeherder → Treeherder: Docs & Development
(Reporter)

Comment 1

3 years ago
camd has an etherpad going of potential tests, so cross referencing them here
https://etherpad.mozilla.org/treeherder-test-checklist
(Reporter)

Comment 2

3 years ago
We might similarly want to run through these smoke tests on an instance eg. stage, before a push to production.
(Reporter)

Comment 3

3 years ago
Camd has migrated the wip test list from etherpad to moztrap
https://moztrap.mozilla.org/runtests/environment/6497
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
(Reporter)

Comment 7

3 years ago
We've been using these tests for a while prior to deployments to prod, they're on Moztrap per above, and will evolve there and some subset perhaps as automated tests. So marking this bug Fixed for now.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
You need to log in before you can comment on or make changes to this bug.