Test Report & Bug-Ticket Generator

A bug report people can actually action

The difference between a ticket that gets fixed and one that bounces back with "cannot reproduce" is usually structure. This generator turns a short form — device, OS / build, operator / PLMN, RAT / band / cell, steps to reproduce, expected vs actual, logs and severity — into a clean, consistent report. The output is plain Markdown, so it renders correctly the moment you paste it into GitHub, GitLab or a Jira description, and there is a plain-text variant for trackers that do not speak Markdown. Copy either one, download the report as a .md file, or print it straight to PDF — everything happens in your browser.

Filling the same fields every time also builds a habit: the reader gets the environment (which handset, which build, which network technology and cell) before the reproduction steps, so they can line up the failure with a log timestamp instead of asking three follow-up questions first.

Scrub identifiers before you share

Logs pulled from a mobile device routinely contain an IMSI, an IMEI, phone numbers and IP addresses — all personal data under the GDPR. The moment that log leaves the lab bench for a shared tracker, an email or an attachment, those identifiers travel with it. Turn on "Scrub identifiers before export" and the logs pass through the same masker used elsewhere on the site, replacing each distinct value with a stable alias such as IMSI_1. The correlation you need for debugging survives while the raw identifier is gone. Nothing is uploaded — the report is built entirely in your browser.