“It worked on my machine.”
On the client’s iPhone, the checkout button sits under the cookie banner.
Manual testing for websites & web apps
Find the bugs before your users do.
Senior manual and exploratory testing for agencies, software houses and product teams without a tester of their own. Clear bug reports, honest coverage and a calmer release day.
Launch Check from €590. QA hours for agencies from €43 an hour.
The tour, in short: find the bugs before your users do. Send the link to what you’re releasing. Comfy clicks through the checkout, forms, phones and edge cases like a real user would, logging what passes and what breaks. You ship with a bug report, not a surprise. A fixed-price Launch Check from €590, or QA hour packs from €49 an hour, down to €43 in bigger packs. testcomfy.com.
10 years testing banking software
Real browsers, real phones
Bug reports developers can act on
Before release
Someone should click through it before your client does.
The people who built a feature know how it’s meant to work. That’s exactly why they rarely use it the way a first-time customer will.
Code is being written faster than ever, often with AI. Somebody still has to try the double click, the back button and the form sent from a slow phone. That’s the job of a tester, and it takes a lot less time than handling bugs after launch.
A 30-minute smoke test before every handover“The client found it first.”
A bug on launch day costs a fix, a re-deploy and some of the client’s trust.
“We tested the happy path.”
Real users paste, go back, refresh and try again. The edge cases are where the bugs live.
What I can test for you
One release, or every release.
Start with a fixed-price check before a launch, or keep a senior tester on hand with a pack of hours your team can use across projects.
Launch Check · from €590
A fixed-price test before you go live
Up to five key user journeys, tested on desktop browsers and real phones before a launch, redesign, migration or big release. You get bug reports in your tracker, a short risk summary and one retest of the fixes.
What’s included
QA hours · for agencies
A tester for your team, by the hour
Prepaid hours you can use across any client or project: pre-release regression, testing new features, retests. White-label on request.
See the hour packs
Test design
Test cases your team can reuse
A regression checklist and test cases written properly, covering boundary values, error states and roles. Delivered in Xray, TestRail or a plain sheet. Your team runs it before every release.
API & UAT
Beyond the screen
REST API checks with Postman and Swagger, end-to-end flows across systems, and help running user acceptance testing with your client.
Not sure what you need?
Send the link and your release date. I’ll suggest the smallest test that covers the biggest risks.
Tell me what to testWhat you get
A bug report your developers will thank you for.
Every bug comes with the steps to reproduce it, what should have happened, what did happen, where, and how much it matters. Usually there’s a recording too.
The summary says what I tested, on which devices, and what I didn’t test. You always know where you stand.
- Straight into Jira, Linear, GitHub, ClickUp or a shared sheet
- Critical bugs sent the moment I find them
- Priority set by user impact, not by volume
CHK-142High
Checkout: the order is placed twice after double-tapping “Pay now” on iPhone
Steps to reproduce
- Add any product to the cart and go to checkout as a guest.
- Fill in valid delivery details and choose card payment.
- Double-tap “Pay now” quickly.
ExpectedOne order, one payment, one confirmation email.
ActualTwo orders are created and the confirmation email arrives twice. Reproduced 3 out of 3 times.
screen-recording.mp4 · 0:14 Not reproduced on desktop Chrome.
For agencies & software houses
No tester on the team? Borrow one for the hours you need.
Most small agencies don’t have enough testing for a full-time hire, so developers check their own work and the project manager clicks through it the night before handover.
Buy a pack of QA hours and use them whenever a project needs testing. One senior tester who gets to know your clients, your stack and the way you work.
QA hour packs and how they work10 hours
€490
€49 an hour
A couple of launches or one busy sprint.
25 hours
€1,150
€46 an hour save 6%
Regular releases across several clients.
50 hours
€2,150
€43 an hour save 12%
A tester on the team for a busy quarter.
The bigger the pack, the lower the hourly rate. Hours are valid for 90 days and work across any of your projects.
How it works
Tell me what’s changing. I’ll tell you what’s broken.
No long onboarding. A link, a date and a test account are enough to start.
-
01
Step 1 · Share
Send the link and the date
What you’re releasing, where it runs and when it has to go live. Staging with test accounts is ideal.
-
02
Step 2 · Scope
Agree what gets tested
Within one working day you get the journeys, devices, price and delivery date in writing.
-
03
Step 3 · Test
Find, report, retest
Critical bugs reach you right away, the rest in the report. Once your team has fixed them, I check again.
About
Hi, I’m Malwina.
I’m a senior QA engineer. For the last ten years I’ve tested software where mistakes are expensive: online banking, insurance and finance platforms, compliance tools and a TV streaming app on web, Android, iOS and Smart TV.
I like finding the one path nobody thought of. I care just as much about describing it so a developer can fix it in minutes, not hours. TestComfy is how I bring that care to smaller teams that don’t have a tester yet.
Projects for
Test design, not just clicking
Test plans, strategies and case repositories built for full requirement coverage, from single features to cross-system end-to-end flows.
Functional to UAT
GUI, regression, integration, API, usability, exploratory and user acceptance testing. Jira, Xray, Confluence, Postman, Swagger, SoapUI, SQL and DevTools.
Lead and mentor
QA lead in a SAFe setup, test manager for a bank client, and mentor to junior testers. Certified in PRINCE2 and AgilePM.
Test Notes
Test design, kindly explained.
How I actually design tests: the techniques, the checklists and the heuristics I use every week. For testers, and for developers who test their own work.
Comfy family
Found bugs? The family can fix them.
TestComfy finds and reports what’s broken. When you need a developer to fix it or to look after the site afterwards, two sister services can help.
FAQ
A few things you might be wondering.
If your project is unusual, tell me about it. Most are.
Ask about your projectIs manual testing still worth it with automated tests and AI?
Yes, because they do different jobs. Automated tests check what someone predicted. Exploratory testing finds what nobody predicted. Most small teams need the second one first, and it’s what tells you which automated tests are worth writing.
Can you guarantee there will be no bugs?
No, and no honest tester can. I test the agreed journeys on the agreed devices, and the report says clearly what was covered and what wasn’t, so you can decide what risk is acceptable.
Do you test on production or staging?
Staging with test accounts and test data is best. If we have to test on production, we agree beforehand which actions are safe, such as test payments or emails that might reach real customers.
Do you fix the bugs too?
No. I find, reproduce and describe them; your developers fix them. If you don’t have developers, the Comfy family can help: WPComfy for WordPress and SiteComfy for other platforms.
How do the hour packs work?
You buy a pack of hours and use it within 90 days across any of your projects. I log time per task in 30-minute steps, so you always see what the hours went on. Details are on the agencies page.
Do you work in Polish?
Yes. I work in English and Polish, and I’m based in Poland (CET).
Release coming up?
Send me the link and the date. I’ll reply within one working day with a scope and a price.
- What you’re releasing
- Where it runs (staging is best)
- When it has to go live
Prefer email? Write to malwina@testcomfy.com · No passwords in the first message, please.