QA Service Terms

We execute agreed test cases against the environment, devices and browsers you specify, and report defects with severity, priority, environment details, reproduction steps, and expected versus actual results.

Testing identifies issues within the agreed scope. It cannot guarantee the absence of all bugs, and passing a test cycle is not a warranty of correctness, uptime or fitness for purpose.

Security checks performed within a QA package are not a security certification, penetration test or compliance audit unless explicitly contracted and delivered by a qualified professional under a separate agreement.

You confirm you own the system under test or hold written authorization to have it tested, and that testing on the supplied environment is permitted by your hosting and third-party providers.

Test credentials are supplied through a secure mechanism, never stored as plain text, restricted to assigned testers, and removed at project close. Use dedicated test accounts and non-production data wherever possible.

Packages that include retesting cover one retest cycle of reported defects after your fixes. Additional cycles or newly introduced functionality are quoted as new work.

Customers receive the QA report, bug list, evidence and status summary. Internal working notes are not part of the deliverable.