Spotify Signup – Manual QA Testing

📌 Project Overview

This project documents a manual QA testing effort focused on the Spotify account signup flow.
The goal was to validate form behavior, input validation, error handling, boundary conditions, and overall usability during account creation.

Testing was performed from a quality assurance perspective, emphasizing both positive (happy path) and negative scenarios to ensure the application handles valid and invalid user input correctly.

---

🎯 Objectives

• Validate signup form functionality with valid user inputs
• Verify error handling for invalid or missing inputs
• Test age restriction logic and password requirements
• Perform boundary testing around critical validation limits
• Identify usability risks and improvement opportunities

---

🔍 Scope of Testing

In Scope

• Email format validation
• Password length requirements
• Required field enforcement
• Date of birth and age restriction checks
• Form submission behavior
• Show/Hide password UI behavior

Out of Scope

• Backend database validation
• Email delivery or verification workflows
• Subscription or payment functionality
• Logged-in user features

---

🧪 Test Types Performed

• Functional Testing
• Negative Testing
• Boundary Testing
• UI Testing
• Exploratory Testing

---

🖥️ Test Environment

• Platform: Web
• Browser: Google Chrome
• Operating System: Windows

---

📄 Test Artifacts

The complete test documentation is provided in the PDF below:

**- Spotify_Signup_Testing.pdf **

This document includes:

• Manual test cases
• Test execution summary
• Coverage breakdown
• Boundary testing results
• Quality and usability improvement observations

---

🐞 Defects

No functional defects were identified during execution of the test cases.
The signup flow behaved as expected for all tested scenarios.

---

💡 Quality Observations

A usability improvement opportunity was identified related to email entry during signup.
This observation is documented as a quality improvement, not a functional defect.

Observations are included for portfolio and learning purposes and do not represent reported defects in the Spotify application.

---

🧠 Key Takeaways

• The signup flow demonstrates strong input validation and error handling
• Boundary conditions around age and password length are enforced correctly
• Negative testing scenarios are handled gracefully
• Usability risks can exist even when functionality behaves as designed

---

📌 Author

Jordyn McIntire
Entry-Level QA Engineer
GitHub: https://github.com/McIntire22