Cross-Device Website Functional Testing
Budget / Salary₹600–1,500
TypeFreelance project
LocationRemote
Posted1 hour ago
We are looking for multiple freelancers to independently test our website, a knowledge contest platform for professionals.
Our objective is to identify functional problems before a wider launch. Each freelancer must complete the full assigned scope and submit their own findings. We need thorough testing from a participant’s perspective, including browsing, registration, login, contest participation, submission, results and badges.
Scope of work
1. Browse and check every public page
Visit every page in the page checklist provided by us. Scroll from the top to the bottom of each page and check:
Menus, submenus, footer links and internal links.
Buttons, dropdowns, filters, search boxes and forms.
Missing content, broken images, overlapping text and horizontal scrolling.
Broken links, incorrect redirects, error messages and pages that fail to load.
Language selection and navigation between translated pages.
This assignment covers the functionality of translated pages. Professional translation proofreading is outside this scope.
2. Test every available login method
Test all login and registration options displayed on the website, including email and the available social login providers.
Check account creation, email confirmation where applicable, login, logout, returning-user login and password recovery for password-based accounts. Also check whether logging in returns the participant to the intended page or contest.
Use accounts you own. Never share passwords, verification codes or access tokens in your report.
3. Complete every active contest
Participate in all contests open for entry during your testing period and complete the final submission for each.
Check:
Contest entry and instructions.
Question display and all question formats encountered.
Answer selection, question navigation and answer saving.
Timer visibility and behaviour.
Final submission, confirmation and result display.
Access to saved results after logging out and logging in again.
Any delay, unexpected refresh, lost answer or submission failure.
Use every available login method during the overall assignment. Record which login method you used for each contest. Do not create duplicate accounts to repeat contests or bypass attempt limits. We will provide a testing allocation if separate accounts are needed.
4. Check results, badges and participant features
Check the participant profile, available privacy controls, results, leaderboards, badge wall and badge downloads.
Where available, verify that:
Downloads produce the correct file and open successfully.
Reports have a professional layout without website menus or clipped content.
Badge QR codes open the correct verification page.
Sharing links and LinkedIn actions open the intended destination.
Public visibility follows the participant’s selected privacy settings.
Testing devices
Each freelancer must test on both a desktop/laptop and a mobile phone. Mention your device, operating system and browser versions in your application. State whether mobile testing uses a physical device or browser simulation.
Required deliverables
Submit:
A completed page checklist showing every page visited and checked.
A login checklist showing the outcome for every available method.
A contest checklist confirming submission and result verification for every active contest.
An issue report containing the page URL, reproduction steps, expected behaviour, actual behaviour, device/browser and supporting screenshots or recordings.
A brief summary of blockers, slow operations and usability concerns.
Clearly separate confirmed functional defects from design suggestions. If you find no issue in an area, record it as tested and passed.
Working arrangements and acceptance
We will hire multiple testers for independent coverage. Each freelancer must complete the agreed scope and submit original evidence. A general opinion or a few screenshots will not count as a completed assignment.
No backend access is required. This is functional testing through normal website use; code changes, vulnerability scanning and load testing are outside the assignment.
Please include in your proposal
Your testing experience, available devices and browsers, estimated completion time, fixed price for the complete assignment, and one example of a well-written bug report.
Our objective is to identify functional problems before a wider launch. Each freelancer must complete the full assigned scope and submit their own findings. We need thorough testing from a participant’s perspective, including browsing, registration, login, contest participation, submission, results and badges.
Scope of work
1. Browse and check every public page
Visit every page in the page checklist provided by us. Scroll from the top to the bottom of each page and check:
Menus, submenus, footer links and internal links.
Buttons, dropdowns, filters, search boxes and forms.
Missing content, broken images, overlapping text and horizontal scrolling.
Broken links, incorrect redirects, error messages and pages that fail to load.
Language selection and navigation between translated pages.
This assignment covers the functionality of translated pages. Professional translation proofreading is outside this scope.
2. Test every available login method
Test all login and registration options displayed on the website, including email and the available social login providers.
Check account creation, email confirmation where applicable, login, logout, returning-user login and password recovery for password-based accounts. Also check whether logging in returns the participant to the intended page or contest.
Use accounts you own. Never share passwords, verification codes or access tokens in your report.
3. Complete every active contest
Participate in all contests open for entry during your testing period and complete the final submission for each.
Check:
Contest entry and instructions.
Question display and all question formats encountered.
Answer selection, question navigation and answer saving.
Timer visibility and behaviour.
Final submission, confirmation and result display.
Access to saved results after logging out and logging in again.
Any delay, unexpected refresh, lost answer or submission failure.
Use every available login method during the overall assignment. Record which login method you used for each contest. Do not create duplicate accounts to repeat contests or bypass attempt limits. We will provide a testing allocation if separate accounts are needed.
4. Check results, badges and participant features
Check the participant profile, available privacy controls, results, leaderboards, badge wall and badge downloads.
Where available, verify that:
Downloads produce the correct file and open successfully.
Reports have a professional layout without website menus or clipped content.
Badge QR codes open the correct verification page.
Sharing links and LinkedIn actions open the intended destination.
Public visibility follows the participant’s selected privacy settings.
Testing devices
Each freelancer must test on both a desktop/laptop and a mobile phone. Mention your device, operating system and browser versions in your application. State whether mobile testing uses a physical device or browser simulation.
Required deliverables
Submit:
A completed page checklist showing every page visited and checked.
A login checklist showing the outcome for every available method.
A contest checklist confirming submission and result verification for every active contest.
An issue report containing the page URL, reproduction steps, expected behaviour, actual behaviour, device/browser and supporting screenshots or recordings.
A brief summary of blockers, slow operations and usability concerns.
Clearly separate confirmed functional defects from design suggestions. If you find no issue in an area, record it as tested and passed.
Working arrangements and acceptance
We will hire multiple testers for independent coverage. Each freelancer must complete the agreed scope and submit original evidence. A general opinion or a few screenshots will not count as a completed assignment.
No backend access is required. This is functional testing through normal website use; code changes, vulnerability scanning and load testing are outside the assignment.
Please include in your proposal
Your testing experience, available devices and browsers, estimated completion time, fixed price for the complete assignment, and one example of a well-written bug report.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.