QA Testing

Senior QA Engineer / QA Automation Engineer We are currently building the platform and are looking for an experienced **Senior QA Engineer / QA Automation Engineer** to take ownership of quality assurance across the product as it develops towards launch. The Role We are looking for a hands-on QA Engineer with strong experience in both automated and manual testing. The successful candidate will establish and maintain the Platform's QA framework, build automated test coverage, manage regression testing and work closely with developers to ensure new functionality is tested thoroughly before release. This is not a purely manual testing role. Strong experience creating and maintaining automated end-to-end tests is essential. Key Responsibilities QA Strategy & Test Management * Develop and maintain the overall QA strategy for Mellowly. * Create and maintain a master test-case library. * Map test cases against the platform's screens, routes and user journeys. * Establish appropriate smoke, regression, integration and end-to-end testing processes. * Maintain pre-release and production release checklists. * Identify gaps in test coverage as the platform develops. * Prioritise testing based on business, technical, privacy and user risk. Automated Testing * Build and maintain automated end-to-end tests using Playwright * Expand the existing Playwright test framework. * Create reusable testing utilities and fixtures. * Implement automated regression tests for critical user journeys. * Maintain visual regression testing. * Ensure automated tests can run reliably within GitHub Actions / CI pipelines. * Investigate failed CI tests and distinguish genuine defects from unstable tests. * Reduce flaky automated tests and improve test reliability over time. Functional Testing Test functionality across areas including: * Public website * Account creation * Login and authentication * Password reset * Session management * Member Dashboard * Clinician portal * Creator portal * Admin portal * Therapy journeys * ADHD and autism assessment journeys * Wellbeing content * Booking workflows * Payments and subscriptions when implemented * Notifications * Profile management * Forms and questionnaires * Search and filtering * Document/report workflows when introduced Form & Validation Testing * Test required fields. * Test validation rules. * Test incorrect and unexpected inputs. * Test error messages. * Test loading, empty, success and failure states. * Test interrupted and incomplete user journeys. * Test save-and-resume functionality where applicable. Authentication & Permission Testing Work closely with developers to test: * Supabase authentication. * User registration and login. * Logout. * Password reset. * Session expiry. * Role-based access control. * Member permissions. * Clinician permissions. * Creator permissions. * Administrator permissions. * Unauthorised access attempts. The QA Engineer should verify that users cannot access records, screens or functionality belonging to another user or role. For example: * Member A must not be able to access Member B's information. * Clinicians must only be able to access information they are authorised to view. * Creator accounts must not have access to clinical or member administration functions. * Administrative permissions must operate according to the defined access model. Database & Backend Integration Testing As the frontend is progressively connected to Supabase: * Test frontend-to-database integrations. * Validate correct data retrieval. * Validate correct data creation and updates. * Test failed database requests. * Test API and server-side error handling. * Test data consistency across related screens. * Verify permission behaviour from an end-user testing perspective. * Support testing of Supabase Row Level Security implementation. The QA Engineer should actively identify permission and data-access issues during testing. Responsive & Cross-Browser Testing Test the platform across: * Desktop * Tablet * Mobile And across major browsers including: * Chrome * Microsoft Edge * Firefox * Safari where available Identify layout, usability and functional differences between devices and browsers. Accessibility Testing Accessibility is an important part. Responsibilities will include: * Automated accessibility testing using **axe-core**. * Lighthouse accessibility checks. * Keyboard-navigation testing. * Focus-state testing. * Basic screen-reader testing. * Text-resizing testing. * Colour-contrast checks. * Reduced-motion testing. Test the Platform's accessibility functionality including: * Calm Mode * Reading Mode * Focus Mode * Reduce Motion * Text Size * Language controls Accessibility issues should be logged, prioritised and regression-tested after fixes. Clinical & Safety-Critical Journey Testing The platform includes mental health and assessment pathways. Approved clinical and safety requirements must therefore be implemented consistently. The QA Engineer will test that approved workflows operate correctly, including areas such as: * Assessment questionnaires. * Consent flows. * Assessment progression. * Appropriate clinician routing. * Urgent-support messaging. * Crisis-support routes. * Safeguarding-related functionality. * Clinical workflow permissions. * Required notices and disclaimers. The QA Engineer will not make clinical decisions or determine clinical policy.. Defect Management For identified defects: * Clearly document the issue. * Provide reproduction steps. * Record expected versus actual behaviour. * Attach screenshots or recordings where appropriate. * Assign severity and priority. * Retest fixes. * Perform appropriate regression testing. * Confirm whether defects can be closed. Critical privacy, security, clinical-safety or data-access issues must be escalated immediately. Example Critical User Journeys The QA Engineer will progressively automate important end-to-end journeys such as: Member Journey Account creation → login → dashboard → recommendation → wellbeing content → support/appointment → follow-up. Therapy Journey Search → therapist profile → selection → booking → payment → appointment → follow-up. Assessment Journey Registration → consent → questionnaire → save progress → submission → clinician review → appointment → report/outcome. Clinician Journey Login → authorised caseload → member/assessment information → workflow actions → notes/results → logout. Creator Journey Login → creator dashboard → content management → analytics → engagement → earnings/payment information. Permissions Journey Attempt to access another user's resources or restricted functionality and verify access is correctly denied. Required Skills & Experience Candidates should have strong experience with: * Software QA and testing. * Automated end-to-end testing. * Playwright. * JavaScript and/or TypeScript. * Web application testing. * Functional testing. * Regression testing. * API/integration testing. * Responsive testing. * Cross-browser testing. * Git. * GitHub. * CI/CD testing. * GitHub Actions or similar CI systems. * Browser developer tools. * Defect management and test documentation. ## Desirable Experience Experience with any of the following would be beneficial: * Supabase. * PostgreSQL. * React. * Next.js. * Accessibility testing. * axe-core. * Lighthouse. * Visual regression testing. * Authentication testing. * Role-based access control. * SaaS platforms. * Healthcare technology. * Mental health technology. * HealthTech. * FinTech or other regulated digital products. * Mobile application testing. Personal Qualities We are looking for someone who: * Is highly detail-oriented. * Thinks beyond the obvious "happy path". * Actively looks for edge cases. * Can work independently. * Communicates defects clearly. * Can challenge implementation constructively. * Understands that quality includes privacy, accessibility and usability — not simply whether a button works. * Is comfortable working in a fast-moving product environment. * Can prioritise critical risks rather than treating every defect equally. * Takes ownership of the QA function. Initial Priorities The successful candidate's initial responsibilities are expected to include: 1. Review the existing application and QA setup. 2. Review the existing Playwright tests. 3. Review GitHub Actions and current CI testing. 4. Establish a master QA test plan. 5. Create a master test-case library. 6. Map tests against the existing screens and routes. 7. Identify critical user journeys requiring immediate automation. 8. Expand Playwright end-to-end coverage. 9. Implement or improve visual regression testing. 10. Expand accessibility testing using axe-core. 11. Test current responsive layouts and browsers. 12. Establish defect-reporting standards. 13. Establish smoke and regression test suites. 14. Progressively add tests as new Supabase-backed functionality is introduced. Working Arrangement This is initially expected to be a short term contract position, with hours increasing as Mellowly approaches major testing and release milestones. We are particularly interested in candidates who can demonstrate practical examples of Playwright automation frameworks or test suites they have personally built. Application Requirements Applicants should provide: * A short summary of relevant QA experience. * Years of software testing experience. * Experience with Playwright. * Experience with TypeScript/JavaScript. * Experience with GitHub Actions or CI/CD. * Experience with accessibility testing. * Experience testing authentication and role-based permissions. * Examples of automated testing frameworks or projects they have worked on. * Current availability. * Hourly rate.