AI Generated the App. How Do You Know It Actually Works?

Generating code is no longer the difficult part.

The harder question is: who verified the behavior of the application after the code was written?

A successful build proves that the project compiled or bundled. It does not prove that:

• A user can complete the main workflow.
• Invalid input is rejected correctly.
• Saved data survives a refresh.
• Unauthorized users cannot access protected actions.
• The preview matches the current code.
• A later change did not break something that previously worked.

For an AI-built application, I believe “done” should require observable evidence from the running product.

A simple verification standard can begin with four checks:

1. Test the successful path

Complete the action exactly as a real user would.

If it is a booking application, create a booking and verify that it appears in the owner dashboard.

2. Test the failure path

Submit invalid information or attempt an action that should be rejected.

A working success screen means little if the application accepts impossible dates, duplicate reservations, or malformed data.

3. Test persistence

Refresh or reopen the application.

If the data disappears, the interface may look complete while the actual product is not.

4. Test a boundary

Attempt one action the current user should not be allowed to perform.

Authentication is not the same as authorization. A user being signed in does not mean every record or action should be accessible.

This verification loop is central to what we are building at Admas: https://www.admas.dev

Admas works inside the project through planning, editing, running, testing, repairing, and previewing—not merely generating files and declaring completion.

The larger principle applies to every AI software-development tool:

Don’t ask only, “Did the agent write the code?”

Ask, “Can I reproduce both success and failure in the running application?”

What evidence do you require before trusting an AI-generated application: a successful build, automated tests, a working preview, or something else?

Disclosure: I’m part of the team building Admas.