40-Hour Web App QA Sprint

I have set aside 40 dedicated hours to put my web application through a full quality-assurance workout. The build must perform flawlessly in Chrome, Firefox and Safari, so every finding has to be reproduced on each of those browsers.

During the engagement I need three complementary perspectives:

• Functional testing – confirm every feature behaves as specced, with clear, reproducible steps when it does not.
• Usability testing – note friction points, confusing flows or visual glitches that might trip up real users.
• Performance testing – baseline page-load times and key workflow response times, flag slow spots and include lightweight stress checks.

Deliverables I expect at the end of the 40 hours:
1. A structured bug/issue log (spreadsheet or Jira export) with severity, browser, steps to reproduce and screenshots or screen-captures.
2. A short usability report highlighting the top improvement opportunities.
3. Performance metrics with before/after numbers for any quick wins you implement or suggest, plus raw output from tools such as Lighthouse, JMeter or browser dev tools.

Feel free to use Selenium, Cypress, Playwright or your preferred test suites; just document the setup so I can rerun the scripts. All materials must be handed over in English.

The clock starts as soon as access credentials are shared, and I will be available for prompt clarification throughout the sprint.