SWE S2026 – Testing Team
Testing folder links: https://drive.google.com/drive/folders/1MD-iqq1I30gbbOU9IJQSvQQUJhHxjcpf https://drive.google.com/drive/folders/1Wlpa510QSLc3mRfsmD1_zA_KcITCopR7
This document describes the Testing Strategy, Tools, Coverage Plan, and Testing Scope for the Social Streaming Platform (SoundCloud Clone).
The Testing Team is responsible for:
- End-to-End (E2E) Testing (≥90% coverage)
- Stress Testing
- API Validation Testing
- Cross-platform testing
- Regression Testing before each phase delivery
- Direct & Corner Case Testing
We follow:
- Incremental Model (Sprint-based testing)
- Test early, test continuously
- Black-box testing for E2E
- API-level validation testing
- Stress testing before each phase delivery
- Regression testing in the final 4 days (push disabled)
| Purpose | Tool | Reason |
|---|---|---|
| E2E Web Testing | Cypress | Fast and reliable browser automation |
| E2E Cross-platform | Appium / Playwright | Android/Desktop automation |
| API Testing | Postman + Newman | REST validation |
| Load Testing | JMeter / k6 | Stress & concurrency testing |
| CI Integration | GitHub Actions | Automated test execution |
| Test Reports | Mochawesome / Allure | Detailed reporting |
Testing Types:
- E2E
- API Testing
- Security Testing
- Token Validation
Planned Tools:
- Cypress
- Postman
- k6
Coverage Includes:
- Valid Registration
- Invalid Email format
- Weak password
- CAPTCHA bypass attempt
- Email verification flow
- Login (valid/invalid)
- JWT expiration & refresh token
- Password reset flow
- Google OAuth flow
Testing Types:
- E2E
- Boundary Testing
Planned Tools:
- Cypress
- Postman
Coverage Includes:
- Edit bio (boundary testing)
- Upload avatar
- Upload cover photo
- Switch account type
- Public vs Private profile
- External links validation
Testing Types:
- Functional E2E
- Concurrency testing
Planned Tools:
- Cypress
- k6
Coverage Includes:
- Follow / Unfollow
- Feed auto-update
- Block user
- Blocked user restrictions
- Suggested users logic
Testing Types:
- File validation
- Boundary testing
- Performance testing
Planned Tools:
- Cypress
- Postman
- JMeter
Coverage Includes:
- Upload MP3
- Upload WAV
- Invalid format rejection
- Large file handling
- Metadata validation
- Visibility toggle
- Processing → Finished state
- Waveform rendering
Testing Types:
- Functional E2E
- Performance Testing
Planned Tools:
- Cypress
- k6
Coverage Includes:
- Play / Pause / Seek
- Volume control
- Recently Played tracking
- Streaming under load
- Region/Tier restrictions
Testing Types:
- Functional Testing
- Edge Case Testing
Planned Tools:
- Cypress
Coverage Includes:
- Like / Unlike
- Repost
- Timestamped comment
- Comment boundaries
- Engagement count accuracy
Testing Types:
- CRUD Testing
- Security Testing
Planned Tools:
- Cypress
- Postman
Coverage Includes:
- Create playlist
- Edit playlist
- Delete playlist
- Add/Remove tracks
- Reorder tracks
- Private playlist access
- Secret token validation
Testing Types:
- Functional Testing
- Performance Testing
Planned Tools:
- Cypress
- k6
Coverage Includes:
- Feed updates
- Search by title
- Search by tags
- Trending logic
- Resource resolver
Testing Types:
- E2E
- Real-time testing
Planned Tools:
- Cypress
Coverage Includes:
- Send/Receive message
- Unread counter
- Share track in chat
- Block messaging
Testing Types:
- Event-based testing
Planned Tools:
- Cypress
Coverage Includes:
- New follower notification
- Like notification
- Comment notification
- Mark as read
- Unread counter accuracy
Testing Types:
- Role-based access testing
- Security testing
Planned Tools:
- Cypress
- Postman
Coverage Includes:
- Report track
- Admin remove track
- Suspend account
- Analytics visibility
- Role authorization checks
Testing Types:
- Payment flow testing
- Business rule validation
Planned Tools:
- Cypress
- Stripe Test Mode
- Postman
Coverage Includes:
- Free plan upload limit
- Premium unlimited uploads
- Mock payment success/failure
- Subscription upgrade/downgrade
- Offline download availability
We simulate:
- 100+ concurrent logins
- 100+ streaming sessions
- Parallel uploads
- Search spikes
- Feed refresh load
Tools:
- k6
- JMeter
- Automated tests will run on Pull Requests
- E2E tests must pass before merge approval
- Coverage target will be maintained ≥90%
| Platform | Target |
|---|---|
| Web E2E | ≥90% |
| Cross Platform | ≥90% |
| Critical Flows | 100% |
/testing ├── e2e/ ├── api/ ├── stress/ ├── selectors/ ├── reports/ └── README.md
All selectors are stored separately as required by project rules.
High-Risk Areas:
- Authentication
- File Upload
- Payment System
- Streaming Engine
These modules receive priority regression and stress testing.
During the final 4 days:
- Full regression testing
- Full stress testing
- No pushes allowed
- Final bug report submission
Responsibilities:
- Designing and maintaining the overall testing strategy
- Managing End-to-End (E2E) testing architecture
- Integrating automated tests with CI/CD pipelines
- Supervising regression testing before each phase delivery
- Coordinating testing activities with other teams
- Ensuring required testing coverage targets are met
Responsibilities:
- Implementing API validation tests
- Assisting in End-to-End (E2E) test automation
- Performing stress and load testing
- Executing automated test suites
- Identifying and reporting bugs and edge cases
- Supporting regression testing and test documentation