Velocity QANina Reweti

MANUAL · UAT · RELEASE · INTEGRATIONS · AI TOOLS

Experienced QA for teams that don't have a QA team.

I'm Nina Reweti. Teams bring me in at release time, when there's no tester on staff or they need an extra pair of hands. I learn the system fast, work inside your process, and tell you plainly what I find. Pay for the days you need. No lock-in.

Email me about your release See the work

10+ years of QA experience · iOS, Android and web · Perth, WA, working remotely

Nina Reweti
Honest, never sugar-coated

WHAT PEOPLE SAY

Most of my work comes from people I've worked with before.

Her contributions to expanding automated testing at MedApps were instrumental in streamlining our release process, enabling our team to launch multiple new in-app features while maintaining an impressive 4.8 App Store rating.
Tom Collins
CEO, MedApps
Working with Nina is a breath of fresh air—you always know where things stand with the product under test, and her feedback is tactful but never sugar-coated.
Read Luke's full recommendation

“Working with Nina is a breath of fresh air—you always know where things stand with the product under test, and her feedback is tactful but never sugar-coated. As the team's QA lead, Nina found many bugs and edge-cases, as well as identifying confusing UI/UX, a testament to her ability to consider how people will actually use the product. She brought that same clarity to Jira and Slack, helping triage customer issues, giving developers the context they needed to act, and keeping everyone in the loop.”

Luke Godeassi
Head of Engineering · worked together at MedApps and Harmonie Health
MORE FROM LINKEDIN RECOMMENDATIONS
“If you ask her to solve a problem for you, she's likely to come back with the problem defined clearly, the fail modes documented thoroughly, potential solutions to any problems that might arise, and further warnings for icebergs you haven't clocked yet.”
Cliff Larner
Founder & Principal Consultant, TinkerTailored
“Medapps has benefitted significantly from her work, with major improvements to the frequency and stability of production releases.”
Henri Scamps
Head of Product · managed Nina at MedApps
“She not only ensures the highest quality in every release but also continuously improves testing processes and automation frameworks.”
Stefano Pezzino
Head of Engineering · same team
“Nina quickly grasps complex features, proactively identifies bugs, and excels at finding system weaknesses.”
Ben Rowland
Hospital Success Manager, MedApps
UAT · MVP WEBSITE LAUNCH
“It was absolutely fantastic working with you and thank you!”
Merran Cooper
CEO, Touchstone Life Care
Read the full recommendations on LinkedIn →

THE WORK

What a finding looks like

Real issues from past work, with client details removed.

BUG REPORT · UAT · INTEGRATION HIGH

Transfer receipt fails to post after a service job uses stock

Cloud ERP (Business Central) · Celigo · field service app
STEPS
  1. Technician completes a job and adds a used part
  2. Integration creates a transfer order in the ERP
  3. Transfer receipt step runs
EXPECTED
Receipt posts, stock lands in the destination warehouse
ACTUAL
Receipt fails: the transfer order ID is not passed to the next step
ALSO FOUND  The transfer order only triggers when a used item is on the job.
Developer confirmed the integration bug and fixed it.

Two more, from different kinds of testing

01 · ON A REAL PHONE

Notification time kept reverting

In a health app, users choose when reminders arrive, for example 2pm Perth time. During release testing, changing the time or time zone did not stick: both reverted to the previous setting.

REPORTED AND FIXED BEFORE RELEASE
02 · AI OUTPUT

AI shortened a privacy policy the lawyers had written

Website content was loaded with an AI tool, and it summarised the privacy policy, dropping wording the lawyers required. Found by checking the live page against the lawyers' original document.

FULL POLICY RESTORED BEFORE LAUNCH

WHAT I TEST

From the phone in someone's hand to the systems behind it

01

Release and regression

The checks that decide whether a build goes out, on iOS, Android and web.

02

User acceptance

Each ticket tested against its acceptance criteria.

03

Integrations

Workflows that cross systems, where each side is often tested on its own.

04

Bug triage

Customer issues reproduced, prioritised and written up so developers can act on them.

05

Automation, talked through

Thinking about automated tests? We work out what is worth automating and what still needs a person. Let's talk →

06

AI tool reviews NEW

Claude skills and plugins checked for gaps and risks. Ask me about it →

I WORK INSIDE YOUR TOOLS JiraTeamworkClickUpSlackMicrosoft TeamsiOSAndroidWebBusiness CentralCeligoClaude
WHERE I TEST iPhone (real device)Android (Android Studio emulators)SafariChrome
SECTORS Health appsERP and field serviceSystem integrationsWebsite launches

HOW WE START

Three steps to get started

  1. 1
    Tell me what's shipping.
    The build, what changed, who uses it, and what worries you.
  2. 2
    I learn the system.
    I map the critical paths and agree priorities with you.
  3. 3
    I test and report.
    Bug reports go into your tracker as I find them, with updates where your team already talks. Test plans or sign-off notes when you want them.

WORKING TOGETHER

Day rate, no lock-in

From $500 a day. Two ways to book:

  • As needed. Book days when a release needs testing.
  • Block booking. Reserve set days for a run of weeks, up to Monday to Friday.

Every contract is different. I quote each one on its requirements and complexity once I know the system and the timeline.

AvailabilityBooked

Days not marked as booked are open. Perth time.

No lock-in contracts. One week's notice either way. Payment and other details are in my terms of engagement.

QUESTIONS

Before you get in touch

Something else on your mind? Use the chat in the corner. If I'm away, leave your email and I'll reply within one business day.

How quickly can you start?

Check the availability calendar above. On open days I can start once the quote is agreed and I have access to your system.

What do you need from us on day one?

Access to the build, environments, tools and test accounts I'll need, a contact who can answer questions, and test data. Please don't send real customer data unless we've agreed it in writing.

Do you work in our time zone?

I'm in Perth and work remotely with teams across Australia. We agree working hours that overlap with your team.

Will you sign our NDA?

Yes. If you don't have one, my terms of engagement cover confidentiality.

What devices and browsers do you test on?

A real iPhone, Android emulators in Android Studio, Safari and Chrome. If your users rely on a specific device, tell me and we'll work out how to cover it.

Do you write test plans?

I work inside your process, so bugs go into your tracker as I find them. Test plans or sign-off notes are available when you want them.

What if you find something serious just before release?

I tell you straight away, with the steps to reproduce it and what it affects, so you can decide. The release decision stays with you.

How does payment work?

Invoiced weekly. The details are in my terms of engagement.

Tell me what's shipping and when.

I'll reply within one business day and tell you plainly whether I'm the right fit.

nina@velocityqa.com.au