Process and delivery

Software QA checklist before launch

Before launch, require evidence that the critical user journeys, permissions, data and recovery behavior meet agreed release criteria. Use this risk-based checklist to decide what must be tested, which findings block release and who accepts the remaining risk.

Book a thirty-minute call

Short answer

A pre-launch QA checklist connects critical journeys, authorization, data integrity, device and load checks, observability and recovery to explicit release decisions. Test depth depends on the consequence of failure; a completed checklist is not a guarantee that no defects remain.

Best for

  • Founders about to put a product in front of paying or enterprise users
  • Teams moving from prototype to a real launch
  • Products where downtime or a data bug costs real money or trust
  • Anyone unsure whether their build is production-ready or just demo-ready

Not for

  • Pure internal throwaway prototypes with no real users
  • Teams that already run mature QA and just want a second pair of hands
  • Products being deliberately killed, not launched
// 01

Compare the options

Compare the evidence for your release, including deliberate approval steps and data-recovery limits.

Area Production-ready Demo that breaks in production
Tests

Automated tests cover the critical paths.

Tested by clicking through it once.

Deploys

Reproducible build and release with agreed approvals and recovery steps.

Manual, from someone’s machine, fingers crossed.

Visibility

Monitoring and error tracking alert you first.

You find out when a user emails, or tweets.

Under load

Tested against realistic concurrency.

Fine for one user, unknown for a thousand.

When it breaks

Tested recovery procedure, with measured time and data-loss limits.

Panic, manual fixes, extended outage.

Security

Auth, secrets, and inputs handled properly.

Hardcoded keys and trusting user input.

// 02

Where Wavect lands on this

Keep the incumbent agency and make QA responsibilities explicit

Independent QA does not require changing the development provider. Before the release, agree four handoffs:

  1. The product owner names the critical journeys, acceptance criteria and release decision-maker.
  2. The tester records the build, environment, steps, observed behavior, severity and evidence for each finding.
  3. The development owner accepts the repair or records why it is deferred; the tester records the retest result.
  4. The release decision-maker reviews unresolved risks and the recovery plan before approval.

Walk one sample finding through that path before commissioning ongoing work. Keep repair and retest scope explicit in both engagements. Transferring accounts and release ownership to a new provider is a separate software takeover.

Choose release checks from the failures that would harm users or the business. Record evidence for the actual build and environment rather than treating a successful demo as production acceptance.

The Twinsoft AI case documents a two-week hardening engagement to enterprise pilot readiness. It does not establish a standard QA duration or full-production guarantee. The tests needed for your release depend on its own interfaces, data and operating risks.

Our software quality assurance service performs the agreed assessment. Remediation, retesting and acceptance must be commissioned explicitly; discovering a finding does not include every possible repair automatically. Monitoring and rehearsed recovery help contain incidents, but recovery time depends on measured system behavior.

Turn the checklist into release evidence

For each critical journey, record the failure consequence, test environment and build, input, expected result, observed result, evidence link and owner. Prioritize payment, permission and irreversible-data failures above cosmetic defects. A passing test count is not a release decision. OWASP ASVS provides security requirements for web applications; select relevant requirements and record the version rather than claiming certification from a generic checklist.

Use a small, explicit mobile matrix

Select supported OS versions and devices from your audience and support policy. Include an older supported device, a small screen and the current release configuration. Test slow and lost connectivity, background/resume, denied permissions, larger text and assistive navigation on the critical journey. For an existing app, install the previous version and upgrade with representative saved data. Android’s testing strategy distinguishes small tests from release-candidate checks; use both according to risk. Sources checked 11 November 2026. This proposed matrix is a starting point, not full device coverage or an accessibility-conformance claim.

Rehearse recovery and access boundaries

Restore a representative backup into an isolated environment and verify record counts, relationships and the business journey. Measure recovery time and the age of recoverable data against agreed objectives. Test old and new application versions against any database migration. If a migration is not reversible, document the forward-repair or restore procedure and how later writes will be reconciled; redeploying code is insufficient.

Use two ordinary accounts and an administrator to test who may read, change, export or delete each sensitive object. Changing an identifier must not grant access to another user’s records. Test expired sessions and revoked roles, not only successful login.

The release record names the product decision-maker and operating owner, open defects, accepted residual risks, alert recipients, rollout conditions and recovery trigger. An unresolved unauthorized-access or data-loss failure should block the affected release. Record a dated decision for lower-severity exceptions. The relevant question is what evidence supports this release, not whether every checkbox is green.

Define when a staged rollout can expand

If the product allows a limited rollout, start with an identified cohort and compare its critical-journey outcomes against the current release where possible. For checkout, track successful paid orders per eligible checkout attempt and reconcile duplicate or missing charges separately.

Set the observation window, minimum sample and stop conditions before rollout. A confirmed duplicate charge can justify stopping immediately even if the overall success rate looks normal. Assign someone to halt expansion, verify what happened to writes already made and choose the agreed recovery path. For a low-volume pilot, use named test journeys and active monitoring rather than relying on a noisy percentage. Google SRE explains how to compare a canary with a control.

// 03

Cost, risk and timeline

Cost Scope-priced QAUse the QA service’s current pricing. Assessment depth, repairs and retesting require an agreed scope.
Risk Silent failureWithout monitoring and rollback, the first you hear of a problem is an angry user and a long outage.
Timeline Twinsoft AI case: 2 weeksTwinsoft AI reached enterprise pilot readiness in two weeks. This describes that case, not a general delivery estimate or full-production guarantee.
// 04

Where this usually goes wrong

  • No automated tests, so every change risks silently breaking something that worked.
  • Manual deploys from a laptop, so releases are stressful and not repeatable.
  • No monitoring or error tracking, so users report outages before you notice them.
  • Never load-tested, so the product folds the first time it gets busy.
  • No rollback plan, so a bad deploy turns into hours of downtime.
  • Secrets in the codebase and unvalidated inputs, so the first probe finds a hole.
// 05

The checklist

Select checks for the release risk. Record who accepts each result and any justified exception.

Tick items off as you go. Nothing is stored or sent.

// 06

What this looks like in our work

These cases document specific engineering contributions. They do not set a universal QA duration, audit coverage or production-readiness guarantee.

These are selected projects, not our full portfolio. We have shipped 100+ products since 2018.

// 07

When this fits, and when it does not

// 01

When Wavect is the right fit

  • You are about to launch and need evidence about how the product handles real users and failures.
  • You have a prototype that demos well and now needs to be production-ready.
  • You need someone to run the QA work, not just hand you a checklist.
  • Downtime or a data bug would cost you real money or a key customer.
// 02

When we are not the fit

  • Your build is an internal throwaway with no real users to protect.
  • You already run mature QA and only need extra hands.
  • You want a paper audit with no one to fix what it finds.
  • You are decommissioning the product rather than launching it.

Agree the assessment, repair responsibilities and retest evidence with the QA service before commissioning work.

// 09

FAQs

Cover the critical journeys, access and data boundaries, relevant devices and load, monitoring, recoverability and operating handover. Agree the evidence and blocking conditions before testing. An irreversible migration may require forward repair or restore rather than code rollback.
Ask for evidence from the release build: critical journeys and failure paths tested, access restrictions verified, incidents observable and recovery rehearsed. The operating owner should understand remaining defects and recovery limits. Passing tests alone does not prove absence of defects.
Start with the failures that would cause the greatest harm. Monitoring, error tracking and a tested recovery procedure are important, but do not replace access-control, payment or data-integrity checks. Measure recovery on your system and agree launch blockers before release.
We can undertake agreed repairs and retesting. The assessment identifies findings; implementation and acceptance are explicitly scoped, including dependencies and any work needing the client or another supplier. Do not assume every discovered issue is included in an assessment fee.
The timeline depends on code quality, integrations, data migration and unresolved risks. Twinsoft AI reached enterprise pilot readiness in two weeks; that published case is not a benchmark for every product. A scoped assessment should establish the work and acceptance criteria before a date is committed.
Book a thirty-minute call