Skip to content

English · 日本語

The showcase suite (the single iOS fixture)

Bajutsu's iOS test fixture lives under demos/showcase/. It is the same app written twice — UIKit and SwiftUI — and each in an accessibility-on / -off variant, so four products (showcase-swiftui, showcase-swiftui-noax, showcase-uikit, showcase-uikit-noax) come from two codebases. It packs the interaction surface a real app has (five tabs with push navigation, all four modal styles, text entry, gestures, async loading, live + mockable networking, an OS-alert screen) into the smallest coherent app that still tells that whole story.

BE-0079 made it the single iOS fixture, retiring the older demo / sample / sample2 apps. The authoritative, screen-by-screen contract — every identifier, every scenario mapping — is demos/showcase/SPEC.md; this page summarizes how to reach it.

Related: scenarios · configuration · codegen · cli

Why two toolkits × two accessibility variants

The showcase makes visible the two axes on which Bajutsu's design rests:

  • Toolkit axis (UIKit vs SwiftUI) — the two accessibility-on products (showcase-swiftui / showcase-uikit) expose an identical identifier contract, so the shared demos/showcase/scenarios/ runs unchanged against either. What differs is the element tree the backend sees, which is exactly what a cross-toolkit driver must absorb.
  • Accessibility axis (no suffix ↔ -noax) — the -noax builds carry no identifiers (idNamespaces: []). They are the controlled experiment for selector stability (DESIGN §5): the same goal recorded against both shows the value of accessibility work as a concrete diff, and they are the record / doctor "missing accessibility" subjects.

Build and run

Registered as four targets.<name> in demos/showcase/showcase.config.yaml (bundle ids com.bajutsu.showcase.ios.{swiftui,uikit}[.noax], deeplink schemes showcase{swiftui,uikit}[noax]). Built with XcodeGen + xcodebuild (project.yml is the source of truth; .xcodeproj / build/ are gitignored).

make -C demos/showcase swiftui-build       # compile the SwiftUI a11y product for the Simulator
make -C demos/showcase run-swiftui         # build → install → bajutsu run (idb) against a booted Simulator
make -C demos/showcase doctor              # the accessibility A/B: a11y grades Ready, -noax Blocked
make -C demos/showcase ui-test             # the codegen path: scenario → XCUITest → xcodebuild test

bajutsu run / serve also build the app on demand via each target's build command, so a manual build is rarely needed.

Launch-environment hooks

Driven via launchEnv and passed as SIMCTL_CHILD_<NAME> (drivers). BE-0079 removed the launch-env shortcuts to a data state and to a pushed screen: the catalog is fixed (no seed knob), and a deeplink no longer jumps onto a detail — a detail is reached only by tapping its row. BE-0107 finished the job by retiring SHOWCASE_TAB, the last launch-env shortcut to a screen: the app always launches on the Stable tab, and every other tab is reached by tapping the native tab bar. Only the XCUITest backend can tap the tab bar (idb collapses it into one opaque group), so the tab-crossing scenarios run on --backend ios. Every screen beyond the launch tab is reached by driving the UI, and a scenario observes the app's own data rather than relying on an injected data state.

Variable Effect
SHOWCASE_UITEST=1 disable animations (keeps condition waits tight)
SHOWCASE_API_URL / SHOWCASE_HTTP_BASE base URLs for the catalog GET and the echo POST/DELETE endpoints

The full identifier catalog, the deeplink grammar, and the primitive-to-scenario mapping are in demos/showcase/SPEC.md.