Browse categories
Explore
Fiverr Pro
English
$
USD
I will qa test your website or web app and report bugs with evidence
Software QA, Release Readiness, Playwright and Cypress
I'm Damo, a software QA professional based in Ireland. I help teams find risks in critical user journeys, assess whether web applications are ready to release, and build reliable Playwright and Cypres...
About this Gig
If you are preparing a release, migration or major change, I will check the user journeys that matter most and review the release evidence you already have.
Before testing, we will agree exactly which journeys, roles, browsers and environments are in scope. I will work through those journeys, record defects with clear reproduction steps and evidence, and review any test results, CI output, release notes or known issues included in your package.
You will receive:
- what I tested and what I did not test
- defects and risks, ordered by impact
- screenshots or recordings where useful
- my view: proceed, proceed with conditions, or hold
- practical next steps
I have worked in software QA since 2017, including Playwright, Cypress, API testing and CI/CD.
This is a focused independent review, not a full regression test or a guarantee that the software is defect-free. Security, performance, accessibility, bug fixing, automation work and retesting are separate scopes.
Please message me before ordering if the work involves payments, several user roles, sensitive data or production access.
Testing application:
Web application
Development technology:
JavaScript
•
Node.js
•
Python
•
TypeScript
Device:
PC
•
Mac
•
iPhone
•
Android mobile phone
My Portfolio
FAQ
What counts as one user journey?
One journey is one complete user goal under one role, such as creating an account and verifying it, or completing checkout and receiving confirmation. A customer flow and an administrator flow normally count as separate journeys.
What release evidence can I send you?
Useful evidence includes release notes, CI results, automated test reports, existing test summaries and known-issues lists. Each item counts as one evidence source. I only need the material relevant to the agreed release.
What do the three release recommendations mean?
Proceed means I found no release blocker within the agreed scope. Proceed with conditions means there are risks to fix or knowingly accept. Hold means the evidence points to a material blocker. Your release owner still makes the final decision.
Does a revision include another round of testing?
No. A revision is for correcting or clarifying the report against the scope we agreed. Testing fixes or changed software is a retest and needs a separate scope or custom offer.
Can you test a live production system?
Only with your clear permission and written restrictions on what I may do. I prefer a staging or test environment, especially where payments, customer data or actions with real-world consequences are involved.
Can you fix the issues or add automated tests afterwards?
Possibly. Bug fixing, automation and wider QA support are not included in this review, but I can assess the findings with you and provide a separate custom offer where the work is a good fit.
