Website QA questions and answers

Quality assurance for a website means checking it against what it is supposed to do before visitors find the gaps. In practice that is testing forms and flows, browsers and devices, accessibility, security settings, search metadata and speed, and recording every failure so it can be fixed and checked again.

In everyday use, close enough. Strictly, testing is the activity of checking, and QA is the wider aim of building quality into a release, including how testing is planned and how fixes are confirmed. On a website project, the difference matters little.

Builders know how the site is meant to work, which makes it hard to see where it does not. An outside tester comes without those assumptions and has no stake in the build looking finished.

No. Testing shows that the things in scope behaved correctly while they were tested, and finds defects where they did not. A clean report means nothing in scope failed; it is not proof that nothing can fail.

Send a brief through the contact page with your launch date, a link to the site and the flows that matter most. The first reply is free, by email, with no obligation.

Staging where one exists, then, if the quote includes it, a short live check after launch. If there is no staging site, we test live with agreed limits, labelling test submissions clearly and avoiding anything that triggers real orders or payments.

Yes, for functional testing. You know your business rules best, and a wrong expectation is cheaper to correct in a test case than in a defect report.

No. Your developer or agency fixes them, and we retest in the rounds the quote lists. Keeping testing separate from building means nobody is checking their own work.

A written report covering the scope, a summary, every defect with evidence and its final status, the test log, and anything knowingly left unresolved.

The platform matters less than the visitor's route through the site. A site on WordPress, another CMS, a hosted builder or custom code can all be tested the same way.

No. It is a WCAG 2.2 sample within QA, using automated tools, keyboard testing and manual inspection. It finds barriers to fix before launch; it does not support a claim of full conformance or replace a dedicated audit.

That depends on what your organisation offers and its size, and it is a legal question for your adviser. The CCPC publishes guidance for businesses, including the exemption for microenterprises providing services.

No. It looks at configuration visible from outside: HTTPS, certificates, headers, exposed files, admin exposure and software versions. A penetration test is a different, deeper service from a specialist.

Our checks behave like ordinary visits. We do not run high-volume scans or try to break in, and we agree in advance which forms can receive test submissions.

The day rate is €520 before any VAT, and each quote shows how VAT applies, and the pricing page lists starting points, such as a small-site pre-launch review from three days. The quote states the days and is fixed before any deposit.

For a small site, around three days of work spread over a week to leave time for fixes before any quoted retest. Larger sites take longer; the quote gives the dates.

Retesting is priced in the quote, which lists the rounds included; anything beyond that scope is agreed in writing first.

Sometimes, depending on the calendar. Less time before launch means less testing can be done, and we say plainly what a short window allows.

No. They run in your browser. Nothing you type is uploaded or seen by us, and it disappears when you close the tab.

Yes. The exports are yours to use however you like.

Because release gates are not equal. Eleven finished gates out of twelve is not nearly ready if the twelfth is the payment flow, so the planner lists what is blocked and open instead.

Yes. We send findings to whoever needs them, including the agency's developers, and can talk through findings with them.

We look at it again together. If the evidence holds, the finding stays, with both views noted. If we were wrong, we correct the report.

Not formally, but we need one named person who can answer questions about business rules and make triage decisions during testing.

Qaveridia is published under its own name, with Samuel Price, a pen name, as editor and writer. The about and author pages explain how the site is run and how to reach us.

Yes. The commercial-interest note in the site footer describes them.

Remotely, for organisations in Ireland and across the EU, in English.