Remote QA Tester / Upgrade Verification Specialist for Drupal Website Upgrades

CodeLift upgrades complex Drupal websites to modern Drupal versions. I am looking for a structured QA tester who can help verify upgraded websites, find regressions, document issues clearly, and support internal sign-off before client UAT or go-live. This is **not primarily a development role**. It is a QA, verification, documentation and quality-control role. You will work on real upgrade projects where we compare old and new website versions, run automated checks, test key flows manually, document regressions, retest fixes, and prepare clear go-live readiness summaries. ## **Responsibilities** You will: * compare old and upgraded website versions * verify items that are marked as “fixed” * follow test checklists for key user flows * review automated test results * identify QA risk areas in upgraded projects * document regressions clearly in Trello / Google Docs * create bug reports with URLs, accounts, screenshots, expected behaviour and actual behaviour * retest fixed issues * maintain QA status per project * prepare internal sign-off / no-go reports * clearly flag go-live blockers ## **Good fit** You are likely a good fit if you are: * very organized * precise and patient * strong in written English * comfortable testing websites * good at following checklists * able to write clear, reproducible bug reports * comfortable working async * able to judge what may be risky in a web project * available with some overlap with Central European Time ## **Nice to have** * Drupal experience * QA testing experience * CMS/web project experience * browser devtools basics * Git or command line basics * Playwright/Cypress experience * experience testing membership, ecommerce or multilingual websites ## **Working style** * remote * async-first * 1–2 short check-ins per week * no daily long meetings * project work is organized in Trello / Google Docs * some work may happen on a prepared remote system with all tools/projects installed * clear written daily updates when work is active ## **Application process** We first review all applications and create a shortlist. Shortlisted candidates will be invited to complete **3 paid, highly relevant trial tasks**. The total expected time is **2–4 hours**. The trial tasks are based on the real work: ### **1\. Regression verification from existing “fixed” docs** You will receive a small list of issues marked as fixed. Your task is to retest them and report: * pass / fail / unclear * URL * test account used * steps tested * expected behaviour * actual behaviour * evidence * whether retesting or reopening is needed ### **2\. QA risk scan of an existing project** You will quickly review an existing upgraded website/project and identify the highest QA risk areas. Examples: * authenticated user roles * member-only flows * multistep workflows * forms * search/filtering * file uploads/downloads * permissions * multilingual pages * emails/notifications * external integrations * admin/editor workflows You will rank the top risks and suggest what should be tested first. ### **3\. Internal sign-off / no-go report** You will receive a small set of QA results and prepare a short internal report: * current QA status * passed items * failed items * blockers * go-live risk * recommended next action * sign-off / conditional sign-off / no-go After reviewing the paid trial tasks, we select the best fit. ## **Working arrangement** We start with an initial **20-hour commitment**. After that, this becomes an **on-demand remote role**, based on project needs. Typical work includes: * upgrade QA * regression testing * retesting fixes * maintenance update verification * test result analysis * internal sign-off reports * Trello / Google Docs documentation Workload may vary per week depending on active projects. ## **To apply** Please include: 1. your QA/testing experience 2. your experience with websites, CMS platforms or Drupal 3. your timezone and availability 4. a short example of a clear bug report you have written, or write one for this scenario: A migrated Drupal website has a contact form. On the old site, submitting the form sends an email and shows a thank-you message. On the new site, the form submits but no email is received. Write the bug report.