Functional behaviour
Forms, account actions, transactions, errors, and expected outcomes.
Independent software testing
Find app and website issues before your customers do.
Plain Morrow Testing checks the user journeys that matter to your business. We document functional bugs and usability friction in a clear report your team can act on before release.
Scoped reviews for websites and applications · Based in South Africa, working worldwide
PLAIN MORROW / SAMPLE FINDING01 / 03
Booking confirmation is missing after payment
Customer impact
A customer may pay successfully but receive no visible confirmation or booking reference.
Steps to reproduce
1.Choose an available appointment.
2.Complete the demo checkout.
3.Observe the blank confirmation area.
ILLUSTRATIVE DEMO · NOT A CLIENT PROJECT
Founded by two cum laude application development graduates with hands-on experience building and testing software.
What we check
Attention where your product needs it most.
We agree on the important journeys first, then test how the product behaves in the environments that matter to your users.
User journeys
The steps people take to sign up, buy, book, manage an account, or complete another agreed task.
Browsers & devices
Agreed desktop and mobile browser combinations, including responsive layouts.
Regression checks
Rechecking key flows after changes or agreed fixes.
Example deliverable
Release Readiness Review
Demo booking application · Illustrative findings only
03Findings
02Journeys
02Browsers
F-01Missing booking confirmationHigh
F-02Reset link feedback unclearMedium
O-01Date selection needs clearer cuesObservation
What you receive
A report built for the next decision.
Findings are separated into confirmed bugs and usability observations, so your team can understand what happened and decide what to fix first.
- Prioritised findings with steps to reproduce
- Screenshots or short recordings where useful
- Device, browser, and environment details
- Customer impact and suggested next action
- A summary of coverage and exclusions
Our process
From scope to clear next steps.
Every review starts with an agreed boundary, so the findings have context and your team knows exactly what was checked.
01
Scope
Agree on the product, important journeys, access, environments, and dates.
02
Test
Work through the agreed scenarios and document evidence.
03
Report
Deliver findings and walk the team through priorities.
04
Retest
Recheck agreed fixes if the quote includes a retest round.
Who we work with
An independent view before a meaningful release.
For product teams preparing a release, agencies handing work to clients, and businesses that want a careful check of a critical digital journey.
The people behind the work
Testing experience shaped by real applications.
Nicholas Farquhar and Jaco Smit each hold a bachelor's degree in Computer and Information Sciences, specialising in application development. Both graduated cum laude.
We have hands-on experience testing BlastPro's web and Android applications for surface blast planning. Sharing feedback during that project shaped our focus on useful, clearly explained findings.
Meet the foundersNF
Nicholas Farquhar
Co-founder · Application development graduate
JS
Jaco Smit
Co-founder · Application development graduate
Experience with BlastPro
Nicholas and Jaco helped test BlastPro's web and Android applications and shared feedback with the project team. This was project experience, not a paid Plain Morrow client engagement.
Read about our experienceCommon questions
What to know before we start.
We keep the scope and access requirements clear before testing begins.
More about our serviceDo you need our source code?
Not for a standard functional review. We agree on access and test accounts during scoping.
Can you test a staging site?
Yes. We prefer a safe test environment with representative test data where possible.
Can you test a live product?
Only within a written, agreed scope and with the owner's authorisation.
Do you provide security penetration testing?
Our initial service focuses on functional behaviour and user journeys. Specialist security testing would be scoped separately.
Start a conversation
Have a release coming up?
Tell us what matters most to your users. We will propose a practical testing scope and a clear quote.