Launchpad

Launchpad
Home Prev	Chapter 20. Testing Guidelines

Reporting a Bug
Confirming and Updating Bugs

Reporting a Bug

Bugs discovered in Sitka’s Evergreen and confirmed on a Evergreen community test server should be reported to Launchpad, the Evergreen community’s bug reporting tool. Once the bug is reported relevant RT tickets should be updated to include the Launchpad bug number.

When reporting a bug include as much information as you can:

the version(s) of Evergreen you have tested.
the browser and version you are using.
the steps to replicate the issue (in a numbered list).
what happened.
what you expected to happen.

Make sure to include relevant screenshots and offical Evergreen tags.

Caution

Screenshots should always be taken using an Evergreen community server. In rare circumstances Sitka’s training server can be used. NEVER post a screenshot to Launchpad taken on a Sitka server that uses production data.

Confirming and Updating Bugs

Sitka staff can mark bugs as affecting them, mark bugs as confirmed, and add additional information about a bug as a comment. Staff can also sign off on bugs that have been tested, usually during Bug Squashing and Feedback Fest weeks.

Some Sitka staff are Evergreen Bug Wranglers and can edit the importance of a bug.

More information about the Evergreen community’s use of Launchpad can be found on their Evergreen Bug Wranger FAQ.