VC LABKnowledge base
Knowledge base: QA and localization in practice
What we explain to clients on the first calls, collected into articles. No theory for its own sake: checklists, scales, templates and examples you can apply in your team.
Knowledge baseWhat LQA isLQA is linguistic testing: checking a translated product in the interface. What LQA looks for, which defects a translation sheet hides, how the process works.Knowledge baseRegression before a promotionRegression before a promotion or sale: what to include in the suite, when to run it, how to prioritize defects and what to check on launch day.Knowledge basep95 and error rateWhat p95, p99, RPS and error rate mean in a load test report, why average response time misleads and how to set thresholds that define a passed test.Knowledge baseA good bug reportThe structure of a bug report fixed on the first try: title, steps to reproduce, expected and actual result, environment, severity and priority, attachments.Knowledge baseTest planThe structure of a working test plan: scope and boundaries, environments and devices, entry and exit criteria, risks, schedule, deliverables. One page.Knowledge baseFormats in CIS countriesHow to write dates, amounts, currencies, phone numbers and addresses in eight CIS countries — from Russia to Georgia. A localization and LQA cheat sheet.Knowledge basePayment testingPayment scenarios to check before release: successful payment, cancellation, gateway timeout, repeated payment, refund, limits, saved cards, webhooks.Knowledge baseFirst-line support playbookA first-line support playbook: request categories, what to resolve yourself, what to escalate and to whom, response and resolution times, tone, templates.Knowledge baseExploratory testingHow to run exploratory testing without documentation: charter-based sessions, timeboxes, notes, turning findings into a checklist and a first regression suite.Knowledge baseWhen to automate regressionWhen a regression suite is ready for automation: case stability, release frequency, the cost of maintaining automated tests, what to automate first.Knowledge baseTesting on budget AndroidWhy an app tuned on a flagship fails for half the audience: memory, weak networks, old Android versions, missing services. What to check and on which devices.Knowledge baseGlossary and translation memoryWhy a product needs a glossary and translation memory, what goes into them, who approves terms, how to connect them to CAT tools and keep them current.Knowledge baseContent moderation rulesModeration rules for user content and promo materials: categories, criteria, a decision scale, a log with justification, escalation and review.Knowledge baseRelease readiness reportWhat a release readiness report must contain: coverage, run results, open defects by severity, risks, workarounds and a recommendation. A one-page template.Knowledge baseWebhook testingHow to test webhooks and external integrations: idempotency, redelivery, out-of-order events, signature verification, timeouts and retries on your side.Knowledge baseContracting an external QA teamWhat a testing contract with an external team must contain: scope and boundaries, deliverables per stage, response times, acceptance, access, pricing.
Tell us about your task
We reply within one business day and send an estimate in 1–2 days. Free of charge.