Precision / release laboratory

A QA and test automation proposal for a software company that tests every release by hand. It covers bugs found by customers, the four kinds of test, the first journeys to automate, the first 90 days, the team, a similar client’s results and three monthly plans.

QA and Test Automation Proposal

<h1 style="font-family:Barlow Condensed;font-weight:600;line-height:1;text-align:left;color:#172D29"><span style="font-size:clamp(42px,11cqw,100px)">QA & test<br>automation</span></h1>

<p style="font-family:Inter;color:#172D29;text-align:left;font-size:18px;line-height:1.5">Proposal for {{CLIENT_COMPANY}}<br>by {{SELLER_COMPANY}}</p>

Overview

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Thank you for the time with your engineers</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">You want to release every week without bugs reaching your landlords and tenants.</p>

Introduction

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Where last quarter’s bugs came from</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">The 14 bugs customers reported, from your support tickets.</p>

Bugs found by customers last quarter, by area

Where bugs come from

<h2 style="font-family:var(--proposal-font-accent);font-weight:500;line-height:1.14"><span style="font-size:clamp(30px,4.2cqw,52px)">We recommend automating your ten key journeys first, then testing every change before it is merged.</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Your developers get an answer in minutes, instead of waiting three days before each release.</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">What we test</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Four kinds of test, each where it is quickest to run.</p>

<p>Playwright tests for the ten journeys on the web app, from tenant sign-up to rent payment.</p>

Key journeys

<p>Fast checks on the 60 endpoints behind payments, maintenance requests and reports.</p>

API checks

<p>Automated checks of login, payments and maintenance requests on iPhone and Android.</p>

Mobile apps

<p>Fresh test landlords, tenants and payments created before every run, so results can be trusted.</p>

Test data

Our recommendation

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">The journeys we automate first</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Five of the ten. The other five are agreed with you in week one.</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">The first 90 days</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Work starts on {{START_DATE}}.</p>

<p>Tests running in your GitHub Actions, test data, and the three journeys behind most bugs.</p>

Month 1

<p>Six more journeys and the API checks.</p>

Month 2

<p>Mobile checks, the last journey and your first weekly release.</p>

Month 3

<p><strong>Not included:</strong> load and security testing, fixing the bugs the tests find, which your developers do, and device cloud time beyond 500 minutes a month.</p>

What is included

Who you will work with

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Results for a similar client</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">A healthcare software company, two quarters later.</p>

Results for a similar client

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Plans and fees</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Three monthly plans. We recommend Growth.</p>

Starter

Growth

New features tested in the sprint they are built.

Scale

<p>Fees are in USD and exclude tax. Device cloud time over 500 minutes a month is billed at cost. This proposal is valid until {{VALID_UNTIL}}.</p>

Plans and fees

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Common questions</span></h2>

<p>No, but they can. The tests live in your repository, and we review any your team writes.</p>

Will our developers have to write tests?

<p>Playwright for the web app, simple HTTP checks for the API and Detox for the mobile apps, all running in your GitHub Actions.</p>

Which tools do you use?

<p>The pull request is blocked, and the failure shows the step, a screenshot and a video. Unreliable tests are fixed or removed within two days.</p>

What happens when a test fails?

<p>Yes, for new features before they are automated. Growth includes four hours of exploratory testing before each release.</p>

Do you still test by hand?

<p>Yes, with 30 days’ notice. Everything we built stays in your repository and keeps running.</p>

Can we stop after three months?

<p>Access to your repository and CI, a test environment, and 30 minutes each sprint with your lead developer.</p>

What do you need from us?

Questions

<p style="font-size:18px;letter-spacing:.08em;text-transform:uppercase">{{SELLER_COMPANY}}</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Next steps</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">How we start.</p>

QA and Test Automation Proposal - Preview