QA audit and process setup
A QA audit at TestLine is an assessment of how your team tests today and a concrete plan of what to change. I can also build the process from scratch: strategy, regression, defect reporting rules and a quality dashboard.
- strategia testów
- plan testów
- Jira
- Jenkins
- GitLab CI
- Azure DevOps
What you get
- An audit report: current process, gaps, risks and change priorities
- A test strategy and plan matched to your release rhythm
- Regression scope, triage rules and defect lifecycle
- A quality dashboard in Jira or Azure DevOps and team onboarding
When it's worth it
The team is growing
What worked with three people stops working with ten. The testing process has to keep up.
Bugs in production
Customers report defects that should have been caught earlier. The audit shows where they leak.
Your first tester
You're hiring a tester and want them to have a starting point. I'll prepare the foundation.
Tests without results
Tests exist, but nobody knows what they say about quality. A dashboard and reports change that.
How I work
- step 1
Interviews
Talks with the team, a review of tools, tickets and the pipeline.
- step 2
Diagnosis
A report with gaps, risks and priorities.
- step 3
Plan
Strategy, regression and defect handling rules.
- step 4
Rollout
Introducing the changes with the team and a dashboard.
Tools
- strategia testów
- plan testów
- Jira
- Jenkins
- GitLab CI
- Azure DevOps
Frequently asked questions
How long does a QA audit take?
Usually one to three weeks, depending on team size and the number of products. We'll set the exact time after the first call.
Do you implement the changes yourself?
I can stay for the rollout: build regression, configure tools and train the team. Or hand the plan over to your people.
Does the audit cover automation?
Yes. I assess existing automated tests and their place in CI, and point out what is worth automating first.
Got a release in a few weeks?
Describe your project in the form. I'll reply with questions about scope or an initial test plan.