Manual + automation QA

Catch bugs.
Not customer complaints.

RockPaper Runway tests websites, web applications and mobile apps before your customers do. Manual testing finds issues real users encounter; automation re-checks critical features on every release.

  • Manual QA
  • Automated regression
  • API & browser testing
RPR QA · Release confidencev2.4.0

Test run / Checkout journey

Release readiness

PAY-007 · High · sticky footer hides the pay button on iOS Safari

Illustrative QA dashboard · not client data · click a check or re-run

Evidence, not assumptions ↗
🧪Manual + automated testing
🇩🇪German telecom software experience
🌍Germany · UAE · India

Experience of our QA lead

The problem

Why bugs reach your customers.

Most production defects were not impossible to find. They were simply not looked for at the right moment, by the right process.

01

Developers test their own work

The experience is checked against what was intended, not what real users will try.

02

Testing starts too late

Quality checks get squeezed into the final days before launch.

03

Old features quietly break

Only the changed code gets tested, and regressions go unnoticed.

04

One browser, one device

A working desktop demo can still fail on mobile or Safari.

05

Bugs get lost in chat

Missing reproduction steps turn simple fixes into long conversations.

06

The same checks repeat

Without automation, every release replays identical manual tasks.

An independent QA process closes the gaps between development, release and real-world use.

The service

What is QA testing?

Quality assurance testing checks that software works as intended before users rely on it. We verify requirements, explore unexpected inputs, test devices and browsers, and report reproducible defects so teams can fix problems before release.

Our approach

Human curiosity.
Machine consistency.

Most software needs both. Explore what manual and automated testing cover and when each creates the most value.

Manual testing services

A tester uses your product like a real person — following planned test cases, then exploring unexpected paths scripts may miss.

  • Functional testingVerify features against requirements and expected outcomes.
  • Exploratory testingFind issues nobody thought to write a test case for.
  • Regression testingRecheck existing features after product changes.
  • Usability testingReveal confusing flows, unclear messages and dead ends.
  • Cross-device testingCheck Chrome, Safari, Firefox and Edge on desktop and mobile.
  • UAT supportProvide scenarios and checklists for stakeholder sign-off.
Manual test session · Checkout
User selects a payment method✓ Pass
Wrong card number displays error✓ Pass
Mobile button remains visible⚠ Defect
Confirmation email arrives✓ Pass

Comparison

Manual vs automation.
Which do you need?

Manual testing discovers new problems. Automation helps make sure known, critical journeys keep working after changes.

Decision pointManual testingAutomation testing
Best forNew features, usability, visual checks, complex journeysRepeated checks, regression, APIs, critical flows
FindsUnexpected problems a script would not look forBreakages in features that used to work
Speed per runHours to daysMinutes
Setup effortLow; testing can start straight awayHigher; scripts must be written and maintained
Cost over timeRises with every releaseFalls as the same tests are reused
When product changes oftenYesOnly for stable parts
Practical rule: test features manually while they are changing, then automate stable checks that must run on every release.

Coverage

Types of testing we provide.

From a single form to a full mobile application, the goal is to find defects where they can actually hurt the user experience.

Functional testing

Confirm every feature follows its requirements, including errors and edge cases.

Regression testing

Check existing functionality after each change.

Integration & API

Verify reliable exchange of data across services, payment systems and CRMs.

Cross-browser & device

Test experience and layout across browsers and screen sizes.

Mobile app testing

Verify permissions, navigation, installations and interruptions on iOS and Android.

Website & e-commerce

Test forms, search, carts, checkout, payments and confirmation emails.

Tooling

Work in your tools.
Not another silo.

We select test frameworks and issue workflows for the product and the team’s existing stack. Exact tool choices are agreed during scoping.

◉Automation frameworks⌘API test tools▣Issue & test management⇢CI/CD integrations

Deliverables

Not just “we found bugs.”
Clear evidence.

You receive a written test plan, reusable test cases, reproducible bug reports, a test summary and, where included in scope, automation scripts in your own repository.

  • Test planScope, devices, methods, exclusions and timeline
  • Test casesSteps and expected results your team can reuse
  • Bug reportsReproduction steps, severity, screenshots and actual vs expected
  • Release summaryPass, fail, open issues and a clear recommendation
  • Automation scriptsIncluded when agreed, with instructions to run
RPR QA / Release summaryv2.4 · Sample
64Passed
3Open issues
7Retested
LOGIN-001Authentication flowPASSED
PAY-007Mobile checkout CTAHIGH
API-004Checkout API validationPASSED

Interactive bug report example

PAY-007 · Mobile checkout button hidden

High severity · iOS Safari

Steps: open checkout on a narrow mobile screen, choose card payment, scroll to the final step.

Expected: the payment CTA remains visible and usable.

Actual: sticky footer overlaps the CTA.

Demonstration only · illustrative test results

Engagement models

Ways to work with us.

One pre-launch check or a QA specialist embedded in your release cycle — choose what matches your product.

Pre-launch test cycle

A complete test of your website or app before release, with a defect list and a retest after fixes.

Ongoing QA alongside developers

A tester joins your release cycle, evaluates new work and runs regression before releases.

Automation setup

We create regression coverage for critical journeys and connect it to your pipeline.

QA for products we build

We also include QA in the products developed by RockPaper Runway.

Process

How testing runs.

A clear sequence from scope to sign-off, with issues documented as soon as they are found.

01

Understand

Review the product, requirements, known issues and priorities.

02

Plan

Agree on a written scope, environments, devices, timeline and quote.

03

Test

Execute manual checks and automate stable, critical flows.

04

Report

Log reproducible defects, evidence and severity.

05

Retest

Check fixes and run regression checks.

06

Sign off

Deliver a test summary and clear release recommendation.

Why RPR

Independent testing.
Integrated thinking.

01

Independent eyes

Testers evaluate what users will do, rather than only what the builders expected.

02

Demanding environments

Our QA lead has tested telecom software in Germany and worked with companies in the UAE and India.

03

Engineering + growth context

We understand how defects in forms, checkout and tracking affect revenue.

04

Actionable reports

Steps, evidence and severity give developers what they need to fix issues.

Pricing

A test plan first.
A quote second.

Pricing depends on product size, device coverage, testing depth, automation needs and whether this is a one-off cycle or ongoing QA.

Scoped to your product

Know exactly what’s covered.

After reviewing your product, we propose a test scope, timeline and quote before work begins.

See pricing

Questions

QA testing questions.

In manual testing a person uses the product and checks the results. In automation testing a script performs the steps and compares results automatically. Manual testing is better at finding new and unexpected problems. Automation is better at repeating the same checks quickly on every release. Most products need both.

Automate a test when the feature is stable, the check has to be repeated on every release, and a failure would be costly, such as login, sign-up, search and checkout. Features that are still changing should be tested manually first, because automated scripts for moving targets need constant rewriting.

Cost depends on product size, the devices and browsers covered, the depth of testing and how much automation is involved. A single pre-launch test of a website costs far less than ongoing QA for an application with frequent releases. We send a test plan and quote after reviewing your product.

A focused pre-launch test of a website usually takes days. A full test cycle for a web or mobile application takes longer, depending on the number of features and platforms. Your test plan includes a timeline, and bugs are reported as they are found, so developers can start fixing immediately.

Yes. Independent testing is most useful when the testers did not build the product. We need access to a test environment, any requirements or designs you have, and your issue tracker. If there is no documentation, we start with exploratory testing and write the test cases as we go.

Yes. We test iOS and Android apps on real devices and emulators, covering installation, navigation, permissions, notifications, interruptions such as calls and poor connections, and behaviour across screen sizes and operating system versions. Critical journeys can also be automated so they are re-checked before each app store release.

You receive the test plan, the test cases used, a bug report for every defect with steps and evidence, and a summary report stating what passed, what failed and whether the product is ready to release. If automation was included, the scripts are delivered in your repository.

Yes. Automated tests can be triggered on every code change or before each deployment, with results posted to your team. A failed test stops a broken build from being released. We connect the suite to your existing pipeline instead of asking you to adopt a new one.

Regression testing re-checks features that already worked after new code is added. It matters because most serious production bugs are old features broken by a recent change. Running a regression suite before every release, ideally automated, is the most reliable way to catch them.

Further reading

The complete guide to QA testing services for SaaS platforms

Read the guide

Let’s make your next release better

Get a test plan for your product.

Share your website or app and tell us what worries you most. We’ll respond with a suggested test plan, timeline and quote.

  • Response within 24 hours
  • Written scope and quote before work begins
  • Manual, automation or both — your choice
  • Clear bug reports your developers can act on