Your way of working, with a QA engineer in it.
Every team ships differently, and your QA engineer fits the way your team does.
We start by listening.
A 30-minute call, with time for your questions. We tell you whether the service is right for you, and if it is not, we say so on the call.
What we ask on the call
- What does your application do, and for whom?
- How does a change get from an idea to your users?
- Who tests today, and how?
- What broke recently that you wish you had caught?
If it is right for you, we propose how to start.
After the call we send a proposal, and we change it with you until you are happy with it.
Scope
The parts of your application we start with, chosen with you.
Rhythm
When testing happens, matched to how you ship.
Budget
One monthly fee for the engineer, the agent and the tooling, sized to the scope.
Engagement
How long, how it continues and how it ends, with notice and a hand-over.
What it is like, day to day.
Your QA engineer works in your channels and tests what you build, as you build it.
A member of your team
Your QA engineer is a regular member of your team. Your developers know them by name and ask them directly.
Your tools
Your tracker, your chat, your environments. Nothing new for your team to log into, unless you want to look.
Your process
Your planning, your reviews, your release steps. Your QA engineer joins them as they are and adds testing where it belongs.
It starts with a 30-minute call.
Tell us about your application and how your team ships, and we tell you how a QA engineer from vikingQA would fit in.