Skip to main content

Dev Station Technology

Software QA services

QA that finds the bugs your users would have found

Manual and automated testing from Ho Chi Minh City for teams in the UK, US and Australia, including the parts that touch hardware, migrations and regulated data.

A regression run before a release

Automated regressionSelenium suite: passed
Device matrixAndroid and iOS: passed
Migration checkRow counts and checksums: matched
Instrument readingBluetooth value against the display
Security passAccess control and data handling

Defects come with steps to reproduce. Your first engagement is usually one release, and you stop there if it was not worth the money.

ZeroRecords lost in the Norwegian migration we tested
6 to 7 hoursAhead of the UK, so results land before your afternoon
3Security test types run on the Norwegian platform
1 releaseThe size of a first engagement
What we test

Seven kinds of testing, each one we have run

Grouped by where the risk sits
Regression and exploratorySelenium suites handed over with documentation, and testers who go looking for trouble.
Migration testingRow counts, checksums and spot checks across both systems.
Devices and instrumentsA real Android and iOS matrix, plus Bluetooth values checked against the display.
Security and release readinessAccess control, data handling, and a go or no-go report before you ship.

Automation pays where a test repeats without changing. Manual testing pays where judgement is needed.

Fit check

Should QA come from outside?

Pick us when

  • Regression takes so long that it gets skipped before a release
  • You are migrating data and cannot afford to lose a record
  • You need a device matrix nobody on your team owns
  • An auditor or a customer wants evidence that testing happened

Look elsewhere when

  • Your product needs deep domain judgement to test at all
  • Releases are small, frequent and low risk
  • Your developers already test each other well
  • Nobody can spare the time to explain the product once
How the work runs

One release first, then a standing arrangement

From learning the product to embedding
Week 1

Learn the product

We work through it with someone from your team and list what is untested.

Week 2

Test plan

Scope, priorities, device matrix, and what to automate. You approve it first.

One release

Run it

A full pass on a real release, with defects logged the way your developers want them.

Ongoing

Embed or hand over

Our testers join your cadence, or we hand over the suites and step back.

Vietnam is 6 to 7 hours ahead of the UK, so results usually arrive before your afternoon.

Technologies

What we test with

Tests run in your pipeline and defects land in your tracker, in your format.

Android logoAndroidiOS logoiOSAzure logoAzure.NET logo.NET
Selenium
Azure DevOps
GitHub Actions
GitLab
Builds

Two engagements where QA carried the risk

National education analytics platform rebuilt by Dev Station
Case study, Norway

Migrating school records with nothing lost

Years of sensitive student data moved onto a rebuilt platform while schools kept using the old one. A separate team worked on migration alone, with security testing covering SPT, SSAT and NVA.

ZeroRecords lost in the migration
Core development team built by Dev Station for a German cloud-native company
Case study, Germany

QA inside a German core team from the first sprint

QA engineers were part of the core team from the start, running manual and Selenium coverage alongside the developers. The engagement grew into a dedicated team plus an on-call group.

On callA support group beside the core team

Tell us what keeps breaking

Three fields. A test lead reads it, and you get a draft test plan within two working days.

  • We look at your release process and what is untested
  • You get a plan, a first engagement scope and a cost
  • No obligation, and no phone number needed to start
FAQs

Questions we get on the first call

Can we start with one release, without a contract?

Yes, and we prefer it. One release gives you a defect report you can judge, and you keep the test plan if you stop there.

Do you write automation, or only run manual tests?

Both. We build Selenium suites and hand them over with documentation so your own team can run and extend them.

Can you test things that touch hardware?

Yes. We have tested apps that read live values from instruments over Bluetooth, where the check is whether the record matches the number on the device.

Do your testers hold certifications?

Several hold ISTQB. We would rather you judge the first release, but the certificates are there if procurement asks.

Give us one release to prove it

Send us the product and how you ship it. You get a test plan, then a full pass on a real release, and a report you can judge on its own.

Let's Talk