Tell us what matters.
Share a link to your app and the features you want checked. We agree on the work, access and price before testing starts.
Look closer.
A checkout example
Paid.
But no order.
Order historyProblem found
!Payment received.
Payment received.
Order missing.
No orders found in the accountWe record what happened
and how to repeat it.
After payment
PaymentCOMPLETED ✓
→OrderMISSING ×
→AccountEMPTY
Payment confirmation
✓
You’re all set.
Your payment was successful.
Thanks for your order.
Back to your account ↗
The payment went through.
Your customer sees a success message and assumes the order is on its way.
Your users shouldn’t
be your testers.
See what
we test.
Try an example test to see how we find problems with payments, accounts, saved changes and smaller screens.
Did the payment
create an order?
We check that a payment creates an order, sends a confirmation and appears in the customer’s account.
- 01Add a product to the basket
- 02Complete a test payment
- 03Check the order confirmation
- 04Find the order in the account
Example only. No real payments or customer data.
Example testREADY
sample-app.test / checkout
orbit®J
YOUR BASKETGood things.
Good things.
On their way.
Form study / 001Object collection$80.00
× 1Order total$80.00
Complete payment →
↳Choose “Run example test” to begin.
Your app.
Our checks.
A clear report.
We agree on what to test, do the checks and explain what needs fixing.
We test it like a customer.
We use people and automated tests to check everyday tasks, mistakes and unexpected inputs.
See what needs fixing.
You get a report with problems ranked by importance and clear steps to repeat them. Your developers can make the fixes, or ask Blu Mint Digital to help.
Sample report
testmorrow.
HIGH PRIORITY
Payment taken.
Order missing.
The payment completes, but the order never appears in the customer’s account.
✓ Payment received PASS✓ Confirmation shown PASS× Order saved FAIL
Example report. No customer data.
Proof.
Not a hunch.
Every report shows what went wrong, why it matters and how your team can repeat the problem.
- Clear steps to repeat each problem
- Screenshots, recordings and test results
- Which problems matter most to your customers
- Follow-up checks on the fixes we agree to test
Before launch.
After launch.
When things change.
Choose a one-off check, regular testing or help with the fixes. We agree on what’s included before you commit.
Before you launch.
+
Find problems before your first customers do. A one-off check of the features you choose.
- Checks of your most important features
- Unexpected entries and smaller screens
- A clear report, explained with your team
- Agreed follow-up checks after fixes
Ongoing testing.
+
Keep improving your app. We check that new changes haven’t broken what already works.
- Repeat checks after product changes
- Scheduled automated tests
- Hands-on checks before agreed updates
- Updated reports and checks after fixes
Testing + fixes.
+
Need help making the fixes too? Add developer support from Blu Mint Digital.
- Regular testing as your app changes
- An agreed amount of developer support
- Fixes by Blu Mint Digital
- Tests to check the fixes work
Before we start, we agree what to test, which browsers to use and how many follow-up checks are included. iOS and Android apps are quoted separately.
Read common questions ↓Your questions,
answered.
Do you need access to our code?
No. We can test through your website or app using a link and test accounts. If you ask us to fix the code too, we agree on that access separately.
What if our app was built with AI?
We test what your customers see and do, whether your app was built with AI, a development team or both. You don’t need to understand the code to get a useful report.
Can you test a live product?
Yes. We agree in advance which actions are safe on your live app. For payments or actions that change or delete data, we prefer a separate test version.
Is this a full security audit?
No. We focus on whether your app works correctly. We can check for some visible issues, such as private pages people can access without signing in, but this does not replace a full security audit.
What does it cost, and how long does it take?
The quote depends on what needs testing, the browsers and devices involved, and how often you need checks. We agree the price, delivery date and included follow-up checks before you commit.
Can our own developers fix what you find?
Yes. Each report gives your team the details they need to investigate and fix the problem. Help from Blu Mint Digital is optional. We can then check the agreed fixes.
Find the bugs.
Before your customers do.
Tell us about your app and what you want tested.