Chat App Comprehensive Testing
Budget: $250 – $750 USD
Our team is about to roll out a new real-time chat application and I need a seasoned tester to run a full sweep before we hit production. The scope spans security, core functionality, and overall usability, with penetration testing sitting at the top of the priority list. I expect you to probe everything from message-plane vulnerabilities to server-side auth flows, validating that encryption, session handling, and role-based access controls can’t be bypassed.
On the functional side, please put message sending and receiving through volume and edge-case scenarios, push the file-sharing module with varied file types and sizes, and verify that user status indicators stay accurate under load or reconnect conditions. I also want candid, UX-focused feedback on flows such as onboarding, settings, and error states so we can tighten any rough edges before launch.
Deliverables:
• A concise test plan outlining coverage of penetration, functional, and usability tracks
• A vulnerability and defect report with severity levels, reproduction steps, screenshots or screen recordings where helpful, and remediation suggestions
• A final summary highlighting overall release readiness and any high-risk items that should block deployment
All testing must be conducted against our staging environment; you’ll receive access credentials and API documentation on kickoff. Tools are at your discretion—Burp Suite, OWASP ZAP, Postman, Selenium, or similar—so long as the results are clearly documented and reproducible.
I’m aiming for a quick turnaround without sacrificing depth. If you’re confident you can deliver actionable insights and clear evidence of coverage, let’s get started.
On the functional side, please put message sending and receiving through volume and edge-case scenarios, push the file-sharing module with varied file types and sizes, and verify that user status indicators stay accurate under load or reconnect conditions. I also want candid, UX-focused feedback on flows such as onboarding, settings, and error states so we can tighten any rough edges before launch.
Deliverables:
• A concise test plan outlining coverage of penetration, functional, and usability tracks
• A vulnerability and defect report with severity levels, reproduction steps, screenshots or screen recordings where helpful, and remediation suggestions
• A final summary highlighting overall release readiness and any high-risk items that should block deployment
All testing must be conducted against our staging environment; you’ll receive access credentials and API documentation on kickoff. Tools are at your discretion—Burp Suite, OWASP ZAP, Postman, Selenium, or similar—so long as the results are clearly documented and reproducible.
I’m aiming for a quick turnaround without sacrificing depth. If you’re confident you can deliver actionable insights and clear evidence of coverage, let’s get started.