Skip to contentTalk to us
العربيةLog inStart free
Test before launch

Before you press Publish, know whether your app is ready

You built your app with Fanann and publishing is the last step. From the publish window itself, the QA engineer tests your app’s most important flows in a real browser and gives you a clear verdict: ready or not ready, and why. Whatever turns up, you ask Fanann to fix, and it is tested again before any customer sees it.

Start freeHow it works
Straight from the publish windowThe decision stays yoursPart of the paid plans
Why before launch

The most expensive bug is the one your customer finds

1

First impressions do not repeat

A customer who tried your app on launch day and hit a broken sign-up usually does not come back, and does not tell you why.

2

You tested it, your way

You know where to click. Your customers leave fields empty, go back and open it on a small phone. That is where the bugs show.

3

The last-minute change

You changed something small an hour before publishing. Does booking still work? Without a test, you are guessing.

1The verdict

Ready, not ready or inconclusive: no flattery

After every test round you see one clear verdict. “Not ready” means a bug that matters was reproduced in this run, and you see it with its evidence. “Inconclusive” means the tests that completed are not enough to judge. Every verdict comes with a list of what was not covered, so “ready” is never read as “bug-free”.

  • The blocking bugs, by name
  • What was not tested is stated plainly
  • Publishing is never silently blocked
2The fix

“Ask Fanann to fix it”, then an automatic retest

Because your app was built here, you do not have to carry the bug to anyone. From the bug card you ask Fanann to fix it, which creates a builder task with the title, the steps and expected vs actual. It is a builder task like any change you request, and it uses your credits. When the fix is built in the preview the retest starts on its own, and “verified fixed” is written only if it passes.

  • From bug to fix task in one tap
  • The retest starts when the fix is built
  • “Fixed” only after a passing test
3The test itself

It knows your app from the first moment

On external sites the QA engineer starts by exploring from the outside. In an app built with Fanann it already knows the pages and the data, so the plan it proposes is closer to what you actually built. It tests the preview before it goes live, in a real browser, and you watch the steps being carried out one by one.

  • Tests the preview before the live version
  • A plan you review before it runs
  • Cases saved and re-run with every publish
Examples

What do you tell it before publishing?

One sentence is enough. Here are three common situations.

Launch is tomorrow

It runs a quick check of the most important flows: sign-up, sign-in, ordering or booking. You get a verdict and a list of what blocks readiness, if anything.

I’m publishing tomorrow. Test the most important things and tell me if it is ready.

A change just before publishing

It re-runs the saved cases for that flow and the ones around it and compares with the previous run: what changed, and whether something that worked has broken.

I changed the booking form. Make sure everything still works as before.

Most of your customers are on phones

It opens the pages at phone screen size in the browser, checks that buttons are visible and forms can be filled and sent, and takes a screenshot of anything that does not look right.

My customers open it on their phones. Test ordering from start to finish at phone size.
The steps

Five steps between “almost ready” and “published with confidence”

All inside Fanann, from the publish window and the QA engineer page.

  1. 1

    Open the publish window

    It shows the last verdict on your app and any blocking bugs, along with the “Test before publishing” button.

  2. 2

    Press “Test before publishing”

    The QA engineer tests the preview version. If it is the first time, it proposes a quick check of the most important flows for you to review before it runs.

  3. 3

    Read the verdict

    Ready, not ready or inconclusive, with what passed, what failed and what was not covered. Every bug has its card and evidence.

  4. 4

    Ask Fanann to fix what turned up

    From the bug card press “Ask Fanann to fix it”. A builder task is created, and when the fix is built the retest starts automatically.

  5. 5

    Publish

    Once the retest passes, publish knowing where your app stands. If you decide to publish despite a warning, that is your call, and it is recorded.

Plainly: what you should know

Not a guarantee“Ready” means what was tested passed. It does not mean the app has no bugs, and what was not covered is listed with every verdict.
Fixes use creditsA fix request is a builder task like any change you ask for in chat, and it uses your credits.
Mobile appsTesting runs in a real browser, including at phone screen size. It does not test native mobile apps on physical devices.
Out of scopeIt does not measure load and it is not a security audit. It tests that your app works as it should for the people using it.
FAQ

Questions people ask

How do I test my app before launch?
In Fanann: open the publish window and press “Test before publishing”. The QA engineer tests your app’s most important flows in a real browser and gives you a readiness verdict and a list of bugs. You ask for fixes, the tests run again, then you publish.
Will Fanann stop me from publishing if there are bugs?
No. Fanann shows the warning and the blocking bugs, and the decision is yours. You can publish after reading the warning, and the fact that you chose to is recorded.
Does it test the live version or the preview?
The pre-publish test runs on the preview version, so bugs show up before they reach your customers. After publishing you can test the live version too, and set what may be changed on it.
What happens after I ask Fanann to fix a bug?
A builder task is created on your app with the bug’s details and the bug moves to in progress. When the fix is built in the preview it becomes ready for retest and the retest starts automatically, as long as your credits allow. If it passes, the bug is stamped “verified fixed”.
What does an “inconclusive” verdict mean?
It means the tests that completed are not enough to judge: too few finished, or many could not run for a reason that is not the app itself, such as a test account that does not work. The report tells you why and what you need to provide.
Do I need technical skills to test my app?
No. You write what you want tested in your own words, in Arabic or English, and the QA engineer proposes the plan, runs it and explains the result in plain language. You write no code and configure no tools.
Is pre-launch testing free?
Signing up to Fanann is free. The QA engineer, the pre-publish check included, is part of the paid plans. Asking Fanann for a fix is a builder task that uses your credits like any change.
QA Engineer

What else can the QA engineer test for you?

QA Engineer

The main page: an AI QA engineer that plans tests, runs them in a real browser, documents every bug with evidence and tells you whether your app is ready to launch.

Meet the QA engineer

Website testing

Is your site built outside Fanann? Add its address and have the QA engineer test its pages, forms and flows in a real browser.

See the details

API testing

Upload the API description file and the QA engineer checks that every request returns what it should: status, fields, permissions and error messages.

See the details

Regression testing

Every test case is saved and re-run. After any change you know in minutes whether what worked still works, and when it broke.

See the details

Bug tracking

Every bug is a card with impact, steps, expected vs actual and a screenshot, and it stays open until a retest proves it fixed.

See the details

For restaurants & booking

Two guests, one table, 7 pm: how the QA engineer finds the double booking before your guests do.

See the details

Guides to read before you test

What is software testing?

An explanation for business owners, without jargon: what gets tested, the kinds of testing that actually matter to you, and when manual testing is enough and when it is not.

Read the guide

Website testing checklist

A practical list to go through before you announce your site: sign-up, forms, checkout, mobile, Arabic, messages and what comes after launch.

Read the guide

How to write a bug report

A ready template and examples: a clear title, steps that reproduce the bug, expected vs actual, evidence, and how to set severity without exaggerating.

Read the guide
Guide: website testing checklistBug tracking to verified fixHosting and one-click publishingControl Center: run your app after launch
From the blog

Guides to testing and AI QA

All Testing & AI QA guides
PASSPASSBUGPASSPASSWhat is an AI QA agent? How it tests your site like a careful person9 min readAn AI product team in one place: plan, build and test without hiring11 min readPASSPASSBUGPASSPASSAI QA agent or a human tester: who should test what?9 min read

Publish knowing, not hoping.

Build your app with Fanann, test it from the publish window, fix what turns up and launch with confidence. The QA engineer is part of the paid plans, and signing up is free.