Run any Skill in Manus with one click

qa-bug-reports-and-regression-tests

Stars1

Forks0

UpdatedFebruary 3, 2026 at 15:44

Writing clear bug reports and converting bugs into regression tests in TryRamadan. Covers precise title, environment, numbered steps, expected vs actual, missing information, and BUG-<AREA>-<ID> test naming. Use when writing or rewriting bug reports, or when adding regression tests from a fixed bug.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ummahbuild

ummahbuild/tryramadan

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	qa-bug-reports-and-regression-tests
description	Writing clear bug reports and converting bugs into regression tests in TryRamadan. Covers precise title, environment, numbered steps, expected vs actual, missing information, and BUG-<AREA>-<ID> test naming. Use when writing or rewriting bug reports, or when adding regression tests from a fixed bug.

QA Bug Reports and Regression Tests (TryRamadan)

Use this skill when writing or rewriting bug reports or when converting a fixed bug into regression tests so reports are actionable and tests are traceable.

1. Bug report format

Title: [Symptom] when [context/trigger/screen]. Example: "Dashboard shows streak 0 after changing Show streak and achievements in Settings."
Environment: Device, OS, browser, app build/version, URL or env.
Reproduction: Numbered steps (1, 2, 3…) that a developer can follow exactly.
Expected vs actual: One clear sentence each; include exact UI text or values when it helps.
Additional context: Screenshots/recordings (with short caption), console/network logs, user state (e.g. first time, has data).
Missing information: List anything that would block a fix (e.g. no console logs, not tested on Safari). See docs/QA-BUG-REPORT-FORMAT-AND-CHECKLIST.md for full template and checklist.

2. Converting a bug into regression tests

Extract core behavior that broke (e.g. "streak must use same 'today' as Dashboard when display timezone is set").
Write 1–3 tests (unit or component) that would have caught the bug: preconditions, steps, expected result.
Naming convention: Describe block: Regression: BUG-<AREA>-<ID> (<short title>). Individual test: BUG-<AREA>-<ID>.<sub>.: <behavior>. Example: Regression: BUG-STRK-001 (streak 0 after Settings / display timezone) and BUG-STRK-001.1: streak uses todayOverride so display-timezone today matches Dashboard.
Area codes (examples): STRK = streak, CAL = calendar/Ramadan, NAV = navigation, SET = Settings, OFF = offline, A11Y = accessibility.
Reference: docs/QA-BUG-REPORT-FORMAT-AND-CHECKLIST.md §7 Bug-derived test naming; docs/QA-TESTING-STRATEGY-AND-LEARNING-PLAN.md for strategy and coverage.

3. Where to add regression tests

Unit/helpers: src/test/loggingAndTracking.test.ts (fasting, streak), src/test/ramadan.test.ts (dates), src/test/countdownAndPrayerTimes.test.ts (time/cache).
Component: Add or extend tests in the relevant feature test file (e.g. dashboardFeatures.test.tsx, onboardingFlow.test.tsx).
Add a comment above the describe referencing the bug report or doc section (e.g. "See Example §5" or ticket).

More from this repository

same repository

tryramadan-project

ummahbuild/tryramadan

TryRamadan app overview, performance optimizations, and resources. Use when making cross-cutting changes, adding dependencies, or optimizing build/runtime.

2026-02-061

culture-recipes-authenticity

ummahbuild/tryramadan

Fact-check and verify culture pages, traditions, and recipes; add and validate hyperlink sources; test authenticity of cultural and culinary claims. Use when adding or editing cultural-traditions.json, recipes.json, country pages, recipe pages, or any tradition/food/recipe content in TryRamadan.

2026-02-051

offline-and-degraded-network

ummahbuild/tryramadan

Offline and degraded network behavior in TryRamadan. Covers cache-first prayer times, API failure/timeout for Aladhan and location/timezone, and what works offline (fasting log, journal, meals). Use when adding features that call external APIs or read/write cached data.

2026-02-031

onboarding-and-re-onboarding

ummahbuild/tryramadan

Onboarding and re-onboarding flows in TryRamadan. Covers step order, persistence (draft vs final preferences), redirect to dashboard, and edge cases (abandonment, skip location, Muslim vs Non-Muslim path). Use when changing onboarding steps, routes, or completion logic.

2026-02-031

performance-cwv

ummahbuild/tryramadan

Web performance and Core Web Vitals (LCP, INP, CLS) in TryRamadan. Covers critical path, lazy loading, images/fonts, and layout stability. Use when changing above-the-fold content, images, fonts, or heavy components on the main route.

2026-02-031

ramadan-calendar-and-fasting-logic

ummahbuild/tryramadan

Ramadan calendar (start/end, day number, year boundary), fasting states (completed/skipped/broken), streak and todayOverride in TryRamadan. Use when editing src/lib/ramadan.ts, fasting state transitions, streak calculation, or Ramadan day labels.

2026-02-031

name	qa-bug-reports-and-regression-tests
description	Writing clear bug reports and converting bugs into regression tests in TryRamadan. Covers precise title, environment, numbered steps, expected vs actual, missing information, and BUG-<AREA>-<ID> test naming. Use when writing or rewriting bug reports, or when adding regression tests from a fixed bug.

QA Bug Reports and Regression Tests (TryRamadan)

Use this skill when writing or rewriting bug reports or when converting a fixed bug into regression tests so reports are actionable and tests are traceable.

1. Bug report format

Title: [Symptom] when [context/trigger/screen]. Example: "Dashboard shows streak 0 after changing Show streak and achievements in Settings."
Environment: Device, OS, browser, app build/version, URL or env.
Reproduction: Numbered steps (1, 2, 3…) that a developer can follow exactly.
Expected vs actual: One clear sentence each; include exact UI text or values when it helps.
Additional context: Screenshots/recordings (with short caption), console/network logs, user state (e.g. first time, has data).
Missing information: List anything that would block a fix (e.g. no console logs, not tested on Safari). See docs/QA-BUG-REPORT-FORMAT-AND-CHECKLIST.md for full template and checklist.

2. Converting a bug into regression tests

Extract core behavior that broke (e.g. "streak must use same 'today' as Dashboard when display timezone is set").
Write 1–3 tests (unit or component) that would have caught the bug: preconditions, steps, expected result.
Naming convention: Describe block: Regression: BUG-<AREA>-<ID> (<short title>). Individual test: BUG-<AREA>-<ID>.<sub>.: <behavior>. Example: Regression: BUG-STRK-001 (streak 0 after Settings / display timezone) and BUG-STRK-001.1: streak uses todayOverride so display-timezone today matches Dashboard.
Area codes (examples): STRK = streak, CAL = calendar/Ramadan, NAV = navigation, SET = Settings, OFF = offline, A11Y = accessibility.
Reference: docs/QA-BUG-REPORT-FORMAT-AND-CHECKLIST.md §7 Bug-derived test naming; docs/QA-TESTING-STRATEGY-AND-LEARNING-PLAN.md for strategy and coverage.

3. Where to add regression tests

Unit/helpers: src/test/loggingAndTracking.test.ts (fasting, streak), src/test/ramadan.test.ts (dates), src/test/countdownAndPrayerTimes.test.ts (time/cache).
Component: Add or extend tests in the relevant feature test file (e.g. dashboardFeatures.test.tsx, onboardingFlow.test.tsx).
Add a comment above the describe referencing the bug report or doc section (e.g. "See Example §5" or ticket).