Crescentek

Quality Assurance Testing

Launch clean. Every time.

Structured QA and pre-launch testing for agencies that can't afford a client-facing bug on go-live day. Functional, cross-device, and performance testing — delivered as a clear, actionable report.

Based in Ireland
GDPR compliant
Reply within 1 working day
QA Issue Tracker
Critical: 0
High: 2
Medium: 5
Low: 8
QA-001High/checkout

Card field loses focus on mobile Safari tap

Fixed
QA-002High/contact

Form submits without email validation

Retesting
QA-003Medium/products

Filter state lost on browser back

Open
QA-004Medium/about

Image alt text missing on team photos

Open
QA-005Low/home

Animation jank on first scroll (Firefox)

Open
5 issues · 2 resolved · 3 openPre-launch sweep complete
What you get

QA that protects your reputation.

Not just a bug list. Structured, actionable output your developer can work through without needing to chase us for clarification.

Structured QA report

Every issue logged with severity (Critical / High / Medium / Low), steps to reproduce, screenshots, and a suggested fix. Not a vague list of complaints.

Regression testing

After fixes are applied, we retest every issue we raised — plus a sweep of adjacent functionality to catch regressions before the client sees them.

Pre-launch sign-off

A structured checklist covering accessibility basics, GDPR compliance points, 404 handling, redirect integrity, and analytics setup — the things that get missed under launch pressure.

Security surface check

Not a full pen test, but a sanity sweep: form injection, exposed config files, mixed content, auth bypass basics, and dependency flag review.

Three testing layers

Functional. Cross-device. Performance.

Every engagement covers all three — because a site that works on your MacBook and breaks on iPhone 11 has failed QA.

Functional
All user flows end-to-end
Form submissions and validation
Navigation and routing
Error states and edge cases
Third-party integrations
Cross-device
iOS Safari, Android Chrome
Desktop: Chrome, Firefox, Safari, Edge
Tablet viewports
Touch interaction testing
Responsive breakpoint audit
Performance
Core Web Vitals (LCP, INP, CLS)
Load time under real conditions
Image and asset optimisation
JavaScript bundle analysis
Server response benchmarking
Common questions

QA and testing questions answered.

The questions Irish SMBs ask us most often.

Staging works fine and is usually preferable — we can test edge cases and error states without affecting real users. We need enough access to navigate the site normally; we don't need code-level access unless we're doing a security review.
Almost always. Internal teams are too close to their own work and have unconscious assumptions about how things work. We approach it as a fresh user with a structured checklist, which consistently surfaces issues that internal testing misses.
Yes. Tell us what your client's customers use — if it's mostly iOS Safari, or a specific version of Chrome, we test on real devices and documented configurations, not just emulators.
A structured document (Google Doc or PDF) with each issue logged as: severity, affected URL, steps to reproduce, screenshot, and suggested resolution. Formatted so your developer can work through it as a task list.
We can. QA-only engagements give you the report and you or your developer fixes it. Full-service engagements include us implementing fixes and retesting. We scope based on what you need.
A standard brochure or small ecommerce site: 2–4 days. Larger sites with complex flows: 5–8 days. We scope time after reviewing the site — we won't quote blind on something we haven't seen.

Don't let a client find the bugs first.

Send us your staging link. We'll scope a QA engagement and tell you honestly what we'd expect to find.

Reply within 1 working day GDPR compliant Based in Ireland