Mobile Guild 5

Live demo

From Jira Story to Verified Mobile Test

Using AI and Maestro to turn acceptance criteria into simulator evidence.

Open calmly: this is not an AI hype talk. It is about connecting artifacts the team already uses.

Mobile Guild 5

02

The whole demo

One story goes in. Verified evidence comes back.

Jira story

→

AI test draft

→

Maestro run

→

Jira evidence

Keep this slide simple. Say: I will start from KAN-4 and end with a video, status, and comment attached back to Jira.

Mobile Guild 5

03

Why it matters

The gap is not writing tests. It is keeping intent and proof together.

01Jira says what we agreed to build.

02The app shows what we actually built.

03Evidence proves the two still match.

This is the key framing for tech leads and engineering managers.

Mobile Guild 5

04

KAN-4Story

Transfer money to a saved beneficiary

User can login with valid credentials

User can select a saved beneficiary

User must review details before confirming

User sees success confirmation after transfer

Starting point

We begin with the same Jira story the team already owns.

No special test management tool. No new workflow for the demo. Just the story and its acceptance criteria.

Tell the room: I will ask Claude Code to fetch KAN-4 through Jira MCP.

Mobile Guild 5

05

The app

AIBank Demo is intentionally small, deterministic, and testable.

Login, dashboard, transfer, review, success. Enough screens to feel real, without live-service risk.

Welcome back

Your demo account is ready.

Available balance 24,850 AED AIBank Demo

Transfer Money

Recent Transactions

Coffee-18 AED

Salary+18,000 AED

Utilities-420 AED

Mention accessibility identifiers only verbally, not as a wall of technical detail.

Mobile Guild 5

06

Live demo

Now I’ll automate KAN-4.

Fetch the Jira story. Generate the Maestro flow. Run it on the simulator. Attach evidence back to Jira.

Stop here and switch to Claude Code / Maestro Studio for the live demo. After the run, advance once to show the recorded evidence.

Mobile Guild 5

07

The payoff

The story gets a receipt.

successful_transfer.mp433spassed

AI-generated Maestro execution completed for KAN-4.

Passed on iOS simulator. Covered login, dashboard, beneficiary selection, review, confirmation, and transfer success. Evidence attached for review.

This is the manager-friendly result: evidence travels back to where the decision happens.

Mobile Guild 5

08

Production reality

To make this reliable, treat automation as a product interface.

Stable selectorsAccessibility identifiers are part of the engineering contract.

Human approvalAI drafts the flow. Engineers approve what matters.

CI evidenceAttach status, video, screenshots, and logs to the story.

Do not make AI the hero. Make the workflow the hero.

Mobile Guild 5

09

Closing

The future is not AI replacing QA or engineers. It is AI closing the gap between what we agreed to build and what we actually verify.

End here. Let the final line breathe.

Mobile Guild 5

10

Thank you

Thank you.

Burak Sakalli
15 May · Dubai

QR code for the Mobile Guild 5 presentation website

Scan or open the deck online

buraksakalli.org/mobile-guild-5

Use this as the final hold slide for questions and conversation.