UI Functional Testing for Web-App
Budget: $30 – $250 USD
I need a Software Quality Assurance (QA) specialist to validate that our web-app UI works end-to-end for three production-facing roles—Student, Teacher, and Campus Supervisor Officer (CSO). This needs to align with the user stories and daily workflows.
Key requirements include:
- Focus on functional testing, primarily user interface (UI) testing.
- Test exclusively on Google Chrome.
Ideal Skills and Experience:
- Strong background in Software Quality Assurance
- Expertise in functional testing, especially UI testing
- Experience with testing on Google Chrome
Functional & Usability Checks:
- Positive + negative paths for every story listed.
- Role-switching: verify session isolation when logging in/out across roles.
- Field validation, error messages, and empty-state UX.
Pluses:
- 3 + years web-app QA experience (SaaS or EdTech a plus)
- Comfortable testing dynamic real-time UIs (WebSockets/SignalR)
- Able to create clear repro steps, concise videos (if needed), and priority triage
What to Test / Core Areas Covered:
Student: Bank, Jobs, Coupons, Hall Passes, Student Store, Badges (6 screens w/sub components)
Teacher: Hall-pass approvals & manual passes (Active and Hall Pass history screens only), Job management inside a class (1 screen w/subcomponents), Store pickups / order fulfillment (1 screen) / Badges. Future phase: Coupon distribution/requests
CSO: Live hall-pass map, active-pass search, student look-ups, incident logging (1 screen)
Basic Github Bug Issue reporting:
Describe the bug / Core Issue Short title – what’s wrong?
Steps to Reproduce Numbered, minimal prerequisites (role, browser, data).
Expected Behavior What should happen per spec/story.
Actual Behavior What you observed, incl. error text or UI mis-state.
Optional: Screenshots, Desktop/Environment, Mobile OS/Smartphone (if any), Additional Context
Access & Timeline
- We will supply one credential set per role, test URL, and demo data seed on award.
- We can reseed/reset test data upon request
- Testing window: 10 business days from access grant; bug-fix re-test window: +2 business days (optional milestone).
Out-of-Scope / Future Rounds:
- Load/performance & security pen-testing, API testing
- Extensive Mobile testing (rendering on mobile is a nice-to have and is not a focus)
- User documentation (there is basic user help in the menu)
- Admin dashboard
- Localization beyond English
- Accessibility
Please provide relevant experience and approach in your bids, final candidates will be given user stories, scripts to help finalize selection.
Key requirements include:
- Focus on functional testing, primarily user interface (UI) testing.
- Test exclusively on Google Chrome.
Ideal Skills and Experience:
- Strong background in Software Quality Assurance
- Expertise in functional testing, especially UI testing
- Experience with testing on Google Chrome
Functional & Usability Checks:
- Positive + negative paths for every story listed.
- Role-switching: verify session isolation when logging in/out across roles.
- Field validation, error messages, and empty-state UX.
Pluses:
- 3 + years web-app QA experience (SaaS or EdTech a plus)
- Comfortable testing dynamic real-time UIs (WebSockets/SignalR)
- Able to create clear repro steps, concise videos (if needed), and priority triage
What to Test / Core Areas Covered:
Student: Bank, Jobs, Coupons, Hall Passes, Student Store, Badges (6 screens w/sub components)
Teacher: Hall-pass approvals & manual passes (Active and Hall Pass history screens only), Job management inside a class (1 screen w/subcomponents), Store pickups / order fulfillment (1 screen) / Badges. Future phase: Coupon distribution/requests
CSO: Live hall-pass map, active-pass search, student look-ups, incident logging (1 screen)
Basic Github Bug Issue reporting:
Describe the bug / Core Issue Short title – what’s wrong?
Steps to Reproduce Numbered, minimal prerequisites (role, browser, data).
Expected Behavior What should happen per spec/story.
Actual Behavior What you observed, incl. error text or UI mis-state.
Optional: Screenshots, Desktop/Environment, Mobile OS/Smartphone (if any), Additional Context
Access & Timeline
- We will supply one credential set per role, test URL, and demo data seed on award.
- We can reseed/reset test data upon request
- Testing window: 10 business days from access grant; bug-fix re-test window: +2 business days (optional milestone).
Out-of-Scope / Future Rounds:
- Load/performance & security pen-testing, API testing
- Extensive Mobile testing (rendering on mobile is a nice-to have and is not a focus)
- User documentation (there is basic user help in the menu)
- Admin dashboard
- Localization beyond English
- Accessibility
Please provide relevant experience and approach in your bids, final candidates will be given user stories, scripts to help finalize selection.
Related categories:
Testing / QA
Software Testing
Test Automation
Website Testing
Regression Testing