Focused Chrome Web App QA
Budget: $10 – $30 USD
I need a diligent QA professional to run an end-to-end functionality test on my web application specifically in Google Chrome. The aim is to catch every functional defect—mis-firing buttons, broken links, faulty form validation, edge-case crashes—before the public launch.
The test will be carried out on our staging server. You’ll receive the URL, sample credentials, and any relevant API keys as soon as we start.
Scope
Although future rounds may cover performance or security, this engagement is strictly about functional behaviour in Chrome. Please explore both desktop and mobile views using DevTools to ensure responsive flows work as intended.
Deliverables
• A concise test plan that maps to all key user journeys
• Executed test cases with pass/fail results
• A bug log (JIRA, Excel, or Google Sheet) that includes steps to reproduce, screenshots or screen recordings, and severity/priority tags
• A closing summary that rates overall stability and highlights high-risk areas
Acceptance criteria
– All critical paths verified and documented
– 95 % or higher coverage of listed user stories
– Every reported issue reproducible in the latest stable Chrome build
Include your estimated turnaround time and the test tools you prefer to use (Selenium, Cypress, Chrome DevTools, etc.). Once completed, I should have clear, actionable feedback and the confidence to move the site into production.
The test will be carried out on our staging server. You’ll receive the URL, sample credentials, and any relevant API keys as soon as we start.
Scope
Although future rounds may cover performance or security, this engagement is strictly about functional behaviour in Chrome. Please explore both desktop and mobile views using DevTools to ensure responsive flows work as intended.
Deliverables
• A concise test plan that maps to all key user journeys
• Executed test cases with pass/fail results
• A bug log (JIRA, Excel, or Google Sheet) that includes steps to reproduce, screenshots or screen recordings, and severity/priority tags
• A closing summary that rates overall stability and highlights high-risk areas
Acceptance criteria
– All critical paths verified and documented
– 95 % or higher coverage of listed user stories
– Every reported issue reproducible in the latest stable Chrome build
Include your estimated turnaround time and the test tools you prefer to use (Selenium, Cypress, Chrome DevTools, etc.). Once completed, I should have clear, actionable feedback and the confidence to move the site into production.
Related categories:
Testing / QA
Test Automation
Website Testing
Usability Testing
Google Chrome
Test Plan Writing
Selenium
API Testing