Table of Contents
Bug Reporting Guidelines
To ensure that bugs are properly reported and efficiently resolved, please follow the structured format below when reporting an issue. A clear and well-documented bug helps the tech team understand and fix problems with fewer follow-up questions.
📝 Required Fields
Each bug report must include the following 5 points:
1. One-line Description of the Issue
* A brief and specific summary of the problem. * Example: Android app crashes when searching for flights from XYZ to ABC on `<Date>`.
2. Steps to Reproduce (How to replicate the issue?)
* List the exact steps to reproduce the issue. * Use the same steps you followed that triggered the bug.
3. Expected Behaviour (What should happen?)
* Describe what you expected to happen. * Example: The app should show available flights.
4. Actual Behaviour (What is happening instead?)
* Explain what is actually happening. * Example: The app closes automatically after tapping “Search”.
5. Screen Recording
* Include a short video or screen recording showing the issue clearly.
⚠️ Common Mistakes to Avoid
- ❌ Vague Report:
“Android app crashing for any product search.” (Too generic, no context or reproducible steps)
- ✅ Proper Report:
“App crashes when searching for flights DXB–LHR on March 15, 2025”