🎶 Sonic Sargam 🧪 - Manual Testing Project

This repository showcases the comprehensive manual testing process conducted for Sonic Sargam, a music application that allows users to create, customize, and share their musical compositions. The focus is on ensuring the application's functionality, usability, and performance meet high-quality standards.

---

📝 Project Overview

Manual testing for Sonic Sargam involved designing test cases, identifying bugs, and ensuring the seamless operation of core features. The testing covered key functionalities, user interactions, and integration points.

---

🎯 Objectives

• Validate core functionalities such as music composition, playback, and export.
• Ensure the application is user-friendly and free from major usability issues.
• Identify and report bugs to the development team for resolution.
• Provide feedback on the app's overall performance and responsiveness.

---

🛠️ Testing Process

The testing process followed a structured approach:

1. Test Plan:

   • Reviewed the application's specification and created the test plan.
   • Identified critical workflows and edge cases.

2. Test Case Design:

   • Created detailed test cases for each module using a standardized format.
   • Categorized test cases into functional, usability, compatibility, and security testing.

3. Test Execution:

   • Executed test cases on different devices and browsers.
   • Logged defects in the bug tracking system (e.g., JIRA).

4. Reporting:

   • Generated detailed test reports with test case results and defect summaries.
   • Shared actionable insights with the development team.

---

📂 Test Artifacts/Files

The following files have been included to document the testing process:

1. Test Plan

• Format: .docx
• Description: It contains complete test plan, how things were going.
• Download: 1. Test Plan Document.docx

2. Mind Map

• Format: .pdf
• Description: It contains complete Mind Map.
• Download: 2. Mind Map.pdf

3. Test Scenarios & Test Cases

• Format: .xlsx
• Description: Contains detailed test cases, including test steps, expected results, actual results, and status.
• Download: 3. Test Scenario & Test Cases.xlsx

4. Bug Reports

• Format: .xlsx
• Description: Detailed bug descriptions with steps to reproduce, expected vs actual results, and screenshots.
• Download: 4. Bug Report.xlsx

5. Test Execution Reports

• Format: .docx
• Description: Consolidated report summarizing the test execution status and findings.
• Download: 5. Test Execution Report.docx

---

🔍 Sample Test Scenarios

Test Case ID	Description	Steps	Expected Result	Status
TC001	Verify user login functionality	1. Open the app 2. Enter valid credentials 3. Click Login	User should be logged in successfully	✅ Pass
TC002	Verify music play, pause tool	1. Navigate to player 2. Click play pause 3. Adjust Musics	Play & Pause tools run without errors	✅ Pass
TC003	performance functionality	1. Navigate to the Website 2. Click F12 3. Go to performance section 4. click record and check	File should open correctly without errors	⚠️ Fail

---

🛡️ Tools Used

• JIRA: Bug tracking and reporting.
• Browser Inspect: Cross-browser testing.
• Slack: For Communication.
• Excel/Google Sheets: Test case documentation.
• Xmind: Mind Map Creation

---

🚀 Project Insights

Key Findings:

• 22 bugs were identified, including 2 critical, 7 major, and 6 minor issues.
• Security testing uncovered vulnerabilities related to SSL implementation.
• Compatibility testing ensured smooth performance across major browsers and devices.

Recommendations:

• Optimize application performance for slower networks.
• Enhance user interface responsiveness.
• Resolve identified bugs to improve stability.

---

🙌 Acknowledgments

• Special thanks to Ajay Dhakkad Sir, Anjali Shaw Mam, Pooja Yadav Mam for guiding the testing process.
• Gratitude to the development team for their collaboration.

---

📧 Contact

For questions or feedback, reach out at:
Email: atulpaldelhi@gmail.com
GitHub: Atul Pal

Web Pages