EvokeQA
All builds
Evoke Host

1.1.0 (53)

iOS TestFlight · API dev-api.evoke.black · channel preview · commit 2377c56

Test cases

57

Testers

0

Passed

0

Failed

0

Bugs & ideas

0

Install Evoke Host 1.1.0 (53) from TestFlight. Work through each checklist, mark Pass or Fail, and describe every Fail. Then spend real time on Try to break it: that's where the bugs hide. Dev talks to live Lenco.

Before you start
  • Money is real. Never request a payout or withdrawal (Account › Payouts). Only cancel events you created that have no paid tickets: cancelling refunds buyers for real. Buy from the attendee app with free, RSVP or K1 tiers only. Ask Emmanuel before anything that touches money.
  • Test data on dev: host org Evoke QA Events (17 events), e.g. k1-test-night (4 tiers incl. hidden K1 Crew, add-ons), victoria-falls-sunset-sessions (40 sold), sunday-park-run-brunch (RSVP, 27 of 30 going), zambia-tech-summit-livestream (online RSVP), k1-charity-dinner (charity), k1-test-fundraiser (running fundraiser). Make your own events for create, cancel and delete tests.
  • Accounts: host login qa.attendee@evoke.test (admin of Evoke QA Events). Ask Emmanuel for the password; it's in the PDF plan, never on this dashboard. For scanner tests, invite your own email as Scanner (Account › Team).
  • Devices: one small iPhone (SE / mini) and one large; the attendee app on a second phone to see what guests see.
What's new
  • Create an event (EVOKE-105 · 352 · 353), #110: Three steps: Basics (type, cover, name, when, where) › Tickets / Guests / Goal › Describe & publish. The end time defaults to start + 3 h, all times are Lusaka time, and a ticketed event starts with one empty tier.
  • Edit an event (EVOKE-357 · 356), #110: Edit is now one page with sections. Save says exactly what will change (“Save 2 changes”), and only those fields are sent. Leaving with unsaved edits asks first.
  • Live & past events (EVOKE-105), #110: A running event can change its description, recap, registration close, waitlist, join link and tiers; other fields are locked with a note. A finished event takes a recap only.
  • Tiers & capacity (EVOKE-105), #110: Adding, pausing or resizing a tier on a live event updates what the attendee app can sell. A sold tier keeps its price and can't shrink below what's sold.
  • Online events (EVOKE-355), #110: Toggle Online, add an https join link. Only people with a ticket or RSVP see the link.
  • Location (EVOKE-163), #110: Search for the venue, drag the pin, or pick a recent venue. With no Google key yet, search uses the phone's maps (Zambia only). No permission prompt on open.
  • Guests told about changes (EVOKE-354), #110: Moving the date, time, venue or join link of a published event notifies ticket holders and RSVP guests. Raising a full event's guest limit tells the waitlist.
  • New Overview, #112: No more “All Stats” tab. One All time card (opens Analytics), then Live now, Coming up and Drafts, with sold or going bars.
  • New event page, #112: Square cover, status line, Lusaka times, Edit / Scan / Insights buttons, and cards for Sales, Guests, Donations, Attendees, Location and About.
  • Bottom bars, #112: Outline icons that turn blue when active, like the attendee app. The + moved to the Overview and Events headers. The Inbox dot only shows for unread messages.
  • Updates over the air, #111: Fixes can reach this build without a new upload. It restarts into an update after 15 min in the background, never over unsaved edits.
  • Sign-in & teams (EVOKE-220 · 233 · 245), #109: Expired sessions, removed members and role changes are handled with a clear notice instead of broken screens.
Reporting
  • Log every Fail in Linear (team Evoke): what broke and where, build, iPhone model and iOS, numbered steps with the test code, expected vs actual, a screenshot or recording, and order numbers for anything with money.
  • Urgent: money moved wrongly, crash on launch, someone else's data. High: a main flow can't be finished. Medium: wrong info, stuck loading. Low: visual glitches.

A · Create an event

EVOKE-105 · 352 · 353

  1. A1

    Do:Overview › + › Tickets event. Name, cover, date, start time, venue, one tier (K1 × 10). Publish.

    Expect:Three steps; end shows start + 3 h; the event appears under Coming up with Lusaka times.

  2. A2

    Do:Create a Free (RSVP) event with a guest limit of 20. Publish.

    Expect:Overview row shows “0 of 20 going”; the attendee app can RSVP.

  3. A3

    Do:Create a Donations event (fundraiser) with a goal.

    Expect:No venue or tickets asked; publishes; event page shows Donations with the goal.

  4. A4

    Do:Name an event “Jazz Night” and go to step 3.

    Expect:A Music category suggestion appears; tapping it fills the category.

  5. A5

    Do:Fill step 1, tap Save draft, leave, reopen it from Drafts, publish.

    Expect:One event only, now published; nothing typed is lost.

  6. A6

    Do:Tap Publish two or three times fast.

    Expect:One event is created, not several.

  7. A7

    Do:Turn on Online and type an http:// link, then an https:// link.

    Expect:http is refused with a clear message; https is accepted.

  8. A8

    Do:Set registration to close after the event ends.

    Expect:Refused: registration must close before the event ends.

B · Edit an event

EVOKE-357 · 356 · 354

  1. B1

    Do:Open your event › Edit. Change only the name.

    Expect:Footer says “Save 1 change”; the sheet lists Name; the page shows the new name.

  2. B2

    Do:Change the date on a published event that has a guest or ticket (attendee app on another phone).

    Expect:A prompt says guests will be notified; the other phone gets the notice.

  3. B3

    Do:Make a change, then tap Back.

    Expect:“Discard changes?” — Keep editing keeps the change; Discard drops it.

  4. B4

    Do:Edit a running event (a fundraiser like k1-test-fundraiser counts).

    Expect:Locked fields say why; allowed ones save. A fundraiser can change its story, goal and end.

  5. B5

    Do:Edit an ended event.

    Expect:Only the recap can be written; it saves.

  6. B6

    Do:On sunday-park-run-brunch set the guest limit below 27.

    Expect:Refused: can't go below the people already registered.

  7. B7

    Do:Raise a full RSVP event's limit while someone is on its waitlist.

    Expect:The waiting guest is told a spot opened.

C · Ticket tiers & capacity

EVOKE-105 · Live Lenco

  1. C1

    Do:On your published ticketed event, add a second tier.

    Expect:It shows in the attendee app; the event's sold-of-total grows.

  2. C2

    Do:On victoria-falls-sunset-sessions try to change a sold tier's price or delete it.

    Expect:Price is locked and delete is refused, each with a reason.

  3. C3

    Do:Lower a sold tier's quantity below what's sold.

    Expect:Refused; the quantity stays.

  4. C4

    Do:On your event with one tier: add a new tier, delete the old one, save.

    Expect:Saves; only the new tier is on sale in the attendee app.

  5. C5

    Do:Pause a tier, check the attendee app, then resume it.

    Expect:Paused: not buyable, stock kept. Resumed: buyable again.

  6. C6

    Do:Tap a tier's quantity or price box.

    Expect:Number pad has a Done bar; dragging the page also closes the keyboard.

D · Location search & map

EVOKE-163

  1. D1

    Do:Open the venue picker on a new event.

    Expect:No location permission prompt just for opening it.

  2. D2

    Do:Search “Arcades”, then “Kabulonga”.

    Expect:Zambia results with a “phone's maps” note; picking one moves the pin and fills the venue name.

  3. D3

    Do:Drag the map somewhere else.

    Expect:Selected place updates to that address; never “Lusaka, Lusaka”.

  4. D4

    Do:Tap Use current location; deny the permission.

    Expect:The message says search and the map still work; nothing breaks.

  5. D5

    Do:Pick a Recent venue.

    Expect:Pin and name come from that venue.

  6. D6

    Do:Back on the form, look at the Where card.

    Expect:Address on top, area under it, nothing said twice.

E · Overview & event page

Redesign · #112

  1. E1

    Do:Open Overview. Read the All time card; tap it.

    Expect:Numbers have labels (no Traffic Score); it opens Analytics.

  2. E2

    Do:Tap See all under Coming up, switch to Drafts, go back and tap See all again.

    Expect:Events opens on Upcoming each time.

  3. E3

    Do:Look at an RSVP row and a ticketed row.

    Expect:RSVP: “x of N going”. Ticketed: “x of N sold · K…”.

  4. E4

    Do:Switch tabs and come back; then pull down on Overview.

    Expect:No jump or gap when coming back; pull shows the spinner and refreshes.

  5. E5

    Do:Open an event: swipe the cover, read the date and time.

    Expect:Gallery dots work; time is Lusaka time; Edit, Scan, Insights buttons.

  6. E6

    Do:Open k1-charity-dinner, then k1-test-fundraiser › See donors.

    Expect:Charity shows Sales; fundraiser lists donors by name, not “No donors”.

  7. E7

    Do:Open an RSVP event's guest list and search a name.

    Expect:Guests filter as you type.

  8. E8

    Do:Tap Share event link on a published event.

    Expect:Share sheet with evoke.black/e/<slug>.

F · Tabs, roles & updates

#111 · #112 · OTA

  1. F1

    Do:Look at the bottom bar on each tab.

    Expect:Outline icons, blue and filled when active; no + in the middle; + on Overview and Events.

  2. F2

    Do:Send yourself a chat message from the attendee app, then read it.

    Expect:Inbox dot appears, then clears once read.

  3. F3

    Do:Sign in as your Scanner account.

    Expect:Events / Scan / Profile bar in the same style; Scan opens the camera; a ticket scans.

  4. F4

    Do:Account › version.

    Expect:Shows 1.1.0.

  5. F5

    Do:When Emmanuel announces an update: leave the app 15+ minutes in the background, open it.

    Expect:It restarts once on the new version; you stay signed in.

  6. F6

    Do:Start editing an event, leave it unsaved, background 15+ minutes after an update is announced.

    Expect:No restart while the edit is unsaved; your changes are still there.

X · Try to break it: be unkind to the app

Edge cases

  1. X1

    Do:Turn on airplane mode, then tap Publish; turn it off and retry.

    Expect:Clear error; retry publishes once; no duplicate event.

  2. X2

    Do:Force-quit the app halfway through creating an event; reopen.

    Expect:No half-made event appears published; drafts you saved are still there.

  3. X3

    Do:Move a published event's date into the past.

    Expect:Refused with a clear message.

  4. X4

    Do:Paste 2,000+ characters, emoji and line breaks into the description.

    Expect:Capped at the limit; line breaks kept; saves.

  5. X5

    Do:Delete every tier on a ticketed event and save.

    Expect:Refused: a ticketed event needs at least one tier.

  6. X6

    Do:Type 0, letters, or 9999999 into tier quantity and price.

    Expect:Blocked or capped; nothing odd is saved.

  7. X7

    Do:Edit the same event on two phones; save different fields on each.

    Expect:The second save doesn't undo the first.

  8. X8

    Do:Switch an event from Tickets to Free mid-create after adding tiers; publish.

    Expect:The free event has no tiers or add-ons in the attendee app.

Y · Try to break it: bad networks, bad timing, wrong role

Edge cases

  1. Y1

    Do:Bad network (Settings › Developer › Network Link “Very Bad Network”), then search a venue.

    Expect:Falls back to phone search or a clear note; dragging the map still works.

  2. Y2

    Do:Turn location off for Evoke Host in Settings; open the picker.

    Expect:Picker works without it; no repeated prompts.

  3. Y3

    Do:Largest text size, Dark Mode, small iPhone: create and edit screens.

    Expect:Nothing cut off or overlapping; buttons reachable.

  4. Y4

    Do:Ask Emmanuel to end your session while you're editing.

    Expect:Clear signed-out notice; no crash.

  5. Y5

    Do:Have someone remove you from the org while you're in it.

    Expect:You're told, and taken out of that org's screens.

  6. Y6

    Do:Background the app during a cover upload; come back.

    Expect:Upload finishes or shows a clear error; no stuck spinner.

  7. Y7

    Do:Switch tabs fast while lists load, on a bad network.

    Expect:No blank Overview and no K0.00 flash after a failed refresh.

  8. Y8

    Do:As a Scanner, open an event edit link someone sent you.

    Expect:No edit access; you stay on scanner screens.