Testing & QA

We find the bugs before your users do

QA is at the heart of developmentVVI. We test AI products, games, e-commerce, web and mobile apps with approaches built for each kind of product.

QA directions

Different products break in different ways. Each direction has its own methods, checklists and tools.

QA of AI products

Testing chatbots, assistants and LLM-based features, where the same input can produce different outputs.

  • Answer accuracy and hallucination checks
  • Prompt-injection and safety testing
  • Bias, tone and policy compliance
  • Regression evaluation sets for model updates

QA of games

Making sure a game is stable, fair and fun on every target platform.

  • Gameplay and progression testing
  • Balance and economy checks
  • Performance, FPS and memory
  • Compatibility across devices

QA of e-commerce

Protecting the money path: catalogue, cart, checkout and payments.

  • Checkout and payment flows
  • Promo codes, taxes, currencies
  • Stock and order statuses
  • Load testing for sales peaks

QA of web applications

Functional and UI testing of sites, portals and SaaS products.

  • Functional and regression testing
  • Cross-browser checks
  • Forms, validation, edge cases
  • Responsive layouts

QA of mobile apps

Testing iOS and Android apps on real devices and conditions.

  • Different screens and OS versions
  • Unstable network and offline
  • Push notifications and permissions
  • App store readiness

API & back-end testing

Checking that services, integrations and data behave correctly.

  • REST and GraphQL testing
  • Contract and integration tests
  • Data integrity
  • Error handling

Test automation

Automated suites that catch regressions on every build.

  • UI tests with Playwright, Cypress, Selenium
  • API test suites
  • CI/CD integration
  • Readable reports

Performance, security & accessibility

Non-functional checks that are easy to forget and expensive to skip.

  • Load and stress testing
  • Basic security checks (OWASP)
  • Accessibility (WCAG)
  • Localisation testing

How our QA process works

Structured, transparent and adapted to your release cycle.

  1. Analysis

    We study the product, requirements and risks, and decide what matters most to test.

  2. Test strategy

    A test plan with scope, priorities, environments and the right mix of manual and automated testing.

  3. Test design

    Checklists and test cases built with proven techniques: equivalence classes, boundary values, decision tables, state transitions.

  4. Execution

    Manual, exploratory and automated runs, with clear bug reports: steps, expected and actual result, evidence.

  5. Report & retest

    Readable status reports, verification of fixes and regression testing before every release.

Types of testing we cover

We combine these to fit your product and your release schedule.

  • Functional
  • Regression
  • Smoke & sanity
  • Exploratory
  • Integration
  • End-to-end
  • UI / UX
  • Usability
  • Cross-browser
  • Mobile
  • API
  • Performance
  • Load & stress
  • Security basics
  • Accessibility
  • Localisation
  • Compatibility
  • Acceptance (UAT)
  • AI evaluation
  • Automated

What you get

Clear artifacts your team can use, not just a list of complaints.

Test plan & strategy

What we test, how, where and in what order, agreed with you up front.

Checklists & test cases

Reusable documentation that stays with your project.

Clear bug reports

Reproducible steps, severity and priority, screenshots and videos.

Automated test suites

Tests that run in your CI and catch regressions on every build.

Status reports

A readable summary of quality: what works, what doesn't, what's risky.

Release recommendation

An honest go / no-go view before each release.

Automation that pays for itself

We automate the checks that run on every build: smoke, API and critical user journeys. People stay free for exploratory testing, where most interesting bugs are found.

  • Playwright
  • Cypress
  • Selenium
  • Postman
  • k6
  • JMeter
  • Appium
  • GitHub Actions

QA knowledge base

The core ideas we rely on every day, explained briefly.

Testing levels

From the smallest piece of code to the whole system.

  • Unit (component)
  • Integration
  • System
  • Acceptance

Test design techniques

Ways to find more bugs with fewer tests.

  • Equivalence partitioning
  • Boundary value analysis
  • Decision tables
  • State transition testing
  • Pairwise testing

Bug life cycle

How a defect travels from discovery to closure.

  • New → Assigned → In progress
  • Fixed → Retest
  • Verified → Closed
  • Reopened if it comes back

Severity vs priority

Two different questions: how bad is it, and how soon must it be fixed?

  • Severity: blocker, critical, major, minor, trivial
  • Priority: high, medium, low
  • A typo on the homepage can be minor but high priority

Testing pyramid

Many fast low-level tests, fewer slow end-to-end ones.

  • Base: unit tests
  • Middle: API and integration
  • Top: a few UI end-to-end tests
  • Plus exploratory testing by humans

Seven testing principles

Classic ideas every QA engineer should know.

  • Testing shows the presence of defects
  • Exhaustive testing is impossible
  • Test early
  • Defects cluster together
  • Repeating the same tests stops finding bugs
  • Testing depends on context
  • Bug-free doesn't mean useful
QA Library

The developmentVVI QA Handbook

Our own free guide to software testing: nine chapters from first principles to automation, AI and processes, with examples, tables and diagrams from our daily work.

Request

Interested in our services?

Tell us about your project: a website, a game, an AI feature or something that needs testing. We'll reply with questions or a first proposal.

  • Free first consultation
  • Reply within 1–2 working days
  • Clear plan, timeline and estimate

Prefer email? Write to us directly:

We are interested in

We use your details only to reply to your request.