Also offered

QA & Testing

Quality assurance that catches problems before your users ever do.

A Putti developer working through code at their desk

QA and testing is the practice of proving software works before your users have to. Quality isn't a phase at the end; it's built in throughout. Putti's QA practice combines test strategy, automation and hands-on testing to give you genuine confidence in every release.

What we cover

  • Test strategy matched to your product and its real risks.
  • Automated testing: unit, integration and end-to-end.
  • Manual and exploratory testing for the things automation misses.
  • Release and regression testing so updates never break what worked.

When you need it

  • Bugs are reaching users and eroding their trust.
  • Releases are slow and nerve-wracking because nothing is automated.
  • You built the product in-house but have no independent QA.
  • Each new feature seems to break an old one.

Why teams choose Putti

We never trade quality for a shortcut, and we bring an independent eye to products whether or not we built them. As a New Zealand team delivering software since 2010 (100+ projects, zero failures), reliable releases are simply how we work.

Frequently asked questions

  • What is QA and why does it matter?

    QA (quality assurance) is the practice of systematically checking that software works as intended before it reaches users. It matters because the cost of a bug rises the later it's found: a problem caught in testing is cheap, while the same problem in production can cost trust, revenue and time.

  • What is the difference between manual and automated testing?

    Automated testing uses code to check behaviour repeatedly and fast, ideal for regression and core flows. Manual and exploratory testing uses human judgement to find the subtle, unexpected issues automation misses. Putti combines both, matched to your product and its risks.

  • Can you test software your team built?

    Yes. We provide QA as a standalone service on products we didn't build, bringing an independent test strategy, automation and hands-on testing to give you confidence in releases without needing an in-house QA team.

  • How do you stop new releases from breaking what already worked?

    Through regression testing, an automated and manual safety net that re-checks existing functionality every time something changes, so updates ship without quietly breaking features users depend on.

  • When should QA start on a project?

    From the beginning. Quality is not a phase bolted on at the end; the earlier testing is designed in, the cheaper and more effective it is. We build a test strategy around your product and risk rather than treating QA as an afterthought.

  • Where is Putti based?

    Putti is a New Zealand software company that has delivered more than 100 projects since 2010 with zero failures, a record built on never trading quality for a shortcut.

Have a project in mind?

We've delivered 100+ projects since 2010 with zero failures, and rescued 20+ that others couldn't finish.

Start a project →