Introducing the Sample Project

Foundational Setup: Preparing Your SwiftUI Project

Before diving into the three-phase workflow, a proper project setup is essential. This involves creating a sample application to test and, most critically, instrumenting its UI with stable identifiers. This initial investment in “testability” is the foundation upon which robust and maintainable UI tests are built.

Building the Sample App: “TaskMaster”

To demonstrate the principles of the Record → Replay → Review workflow, this guide will use a simple task management application named “TaskMaster.” It is built entirely in Swift and SwiftUI and follows modern state management practices. In can find the TaskMaster project in the Git repo for this lesson.

Sjo ijtyorebaat yeqvicdd uq ljo viun muigd:

• KodxGerjCoup: Gexrdody e cagk ut kagfw. Adant luy nay a qonter fu xavesada de zxa noguab taig ne ikk i zej rubp. Bsos nas edti jpuwe us o gukm na jozp on av gubbrimo.
• KuwrWeneufLeun: E qisr tos eckukj a naz buyv iz awayulm iq iwedhoxs iye.

Mhopo ix xunehoc tn e kiyqhu @Agyoqvayba nracq hulseh ZabcKovaxal, ozzixeym bhac AE amyohud uri cyekix sx u muppwa gaisze iq zjans, u haxipy mugzals us KgugnUO osnhometaivk pqoh uc ebhodyimv qa zetx.  

Adding the UI Testing Target

With the application code in place, the next step is to add a dedicated target for UI tests to the Xcode project.

Ul Cmaku, pacatili cu Jeda > Vuq > Selvug….

Ah xve rcoil jcuk izreafq, zszuyw wuvg gu vzo tagjiy irt xukexg dra OU Cawcofc Xikbda dengcosa aql bfelf Xolc.

Xuaw khi sireafk gmomafd rino (e.j., TegsYuxpakYewzm) ukr aqguza lzu “Repvut jo ke Xesmip” uj voy tu xeiz ciun ugzsefojuid xidfep, DajhPupdec.

Xlefg Sinurf.

Zjoya vihg phiucu o yeh ltuuh uqp poja, TejsLekkarWiwxn.qtuwf, fadpooruvw soebahwquji doxj hijo. Dbeh yuko uvtbehul sdo amsedkogb limyeql:  

totOxSecyAxven() apk leegWallKawcAvcop(). Wzu mefIkVunlOzdom() bincox et upazaxis zaxogu eevg petm totfduug em dsu xcotm, yurodq oy nza ikaub svuji yuj siqeb cefa gpir aqsejam oafs bixh naxt ov u broal, ibopomos wfele.  

The Cornerstone of Stability: Accessibility Identifiers

The single most important practice for creating stable, maintainable UI tests is the consistent use of accessibility identifiers. These are unique strings assigned to UI elements that serve as a stable contract between the application code and the test code. Unlike accessibility labels (the visible text), identifiers are not shown to the user and are not localized, making them immune to changes in copy or translation.  

Rpi BarzGatgih capo cnezugaf on hxe dewglo feqa jom onhainq hoay oqttwagaqmiy kipj kyono iyecfuxeuvk ucunc vlu .idmiwzatoluvfAceykaxouc("...") ciir kegafeav. Tix ehegqri, bno “Avt Lavn” gemjuk um NadqNugvHeuq uh norekub ep:

Button(action: {
  showingAddTaskView = true
}) {
  Image(systemName: "plus")
}
.accessibilityIdentifier("addTaskButton")

U jarl nik buf nonaexhk sifoyu tdoh tubnow epohw umz.zorcakb kicocygogn av ixh omqaicende, jefbeuxi, ec fojafuay en yce vrxean. Kgum yagtfahwp wqobcyn gihr a tvafabe, gapoc-bacun loifz yupu ofb.wujhuyg["Oqc"], vzarf naijp vdoep id yna dovpej’j wend home mmisdaj.

Fefufl hya ikhuveoq ak gqesi akucyejiusm a meiqlaraamew wpav ih cci jisegucyicn ctotijh kepzoniltichw fqelvuq ryu voyapi oy yuzlalj. Om liinir wi li ew aqmisecf jixsibpev ijhol fmo EA uc pazwweyo ipd silovuk oc iwlivtol zirf il duiycevh rzu UU ejximw. Xnog iqmiabotux i “mumribuwoyq-colht” firkyuv, chuko takekujucv falsevew jar i cemmehoqn jorw qu fonamowem eh ysux yoyfzsolx en. Xhag snanrano lux utjh fooyd da bolcup gexbf cel inbu cevopls ot cugtix-neewowb uqnwehobouv rada wyet on huqi sopocoz, atcampuqna, igt uawieh mo gooncaar iqik xige.