LamaGlam
Talk about a project

Team & partnership — sold as a team, over time

QA
& testing

Test plan, structured campaigns, reports your devs can actually read. From pre-production to post-launch follow-up.

The coverage

Where we
test

An in-house device lab for PC and mobile, your development kits for console. We tell you which one applies before quoting, not after.

PC / Steam In-house lab
iOS In-house lab
Android In-house lab
macOS In-house lab
PlayStation On client devkit
Xbox On client devkit
Nintendo Switch On client devkit
Cloud gaming On client access

On console we test from your development kits or your publisher’s: your platform accounts and credentials stay with you, and so does the final submission.

The scope

What we
test

Eight kinds of passes, ordered on their own or combined into a campaign. We tell you which ones your build actually deserves before selling them to you.

Campaign core

Functional

Game flow, systems, saves, economy and edge cases.

Certification

Platform compliance

Certification checklists, mandated terminology, system messages.

Device lab

Compatibility

Configurations, OS versions, controllers, resolutions and aspect ratios.

Device lab

Performance

Frame times, memory spikes, load times, long-session stability.

Localisation

LQA

Truncations, overflows, terminology consistency, missing strings.

Comfort

Accessibility

HUD legibility, contrast, text size, control remapping.

Milestones

Regression

Fix verification and a full pass over the areas touched.

Tooling

Automation

Smoke tests and scripted passes, wired into your continuous integration.

The deliverables

What you
get

Nothing like an unreadable end-of-month report: findings you can act on as they land, filed straight into your own tool.

Campaign slipLamaGlam — QA & testing
Before the campaign

Test plan

A coverage matrix and a scope agreed with you before the first pass.

Document + matrix
During

Tickets in your tool

Reproducible and prioritised, with the exact build and configuration, filed as they land.

In your tracker
Every pass

Campaign summary

Priorities at the top of the report, and the bug curve in numbers.

One report per pass
Before the gate

Go / no-go recommendation

What blocks, what can wait, what we knowingly let through — and why.

Written note

Frequently asked

What we get
asked
first

If your question is not here, write to us: we answer within 48 working hours, including when the answer is no.

We fill in certification checklists line by line, test against the target platform’s requirements and work the feedback through to acceptance. Submission itself stays with you or your publisher, with your own platform accounts and credentials.

Yes, as long as your build exposes a way to drive it. We start with an audit: what can be automated at your end, what never will be, and what it costs to write and then maintain. The tests then run on your continuous integration, not ours.

Yours. We file tickets in Jira, Linear, Notion, GitHub or whatever you already use, with your fields and your severity levels. We will never ask you to adopt our tool to read our reports.

On request, with native testers of the target language. Tell us the languages and we tell you which ones we can cover. We would rather turn a language down than subcontract it blind: LQA done by a non-native is worth nothing.

That is the most common case: test volume doubles or triples as a milestone approaches. We size the team with you in advance, hold the peak, then scale back down. Warn us a few weeks ahead rather than the day before.

Yes: an agreed volume of passes each month, with the same team from one month to the next. It works best on a live-service game, because the testers end up knowing the game better than some of your own developers.

Contact

Let's talk about
your project.

Reply within 48 working hours.

Type of need