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.

Gzu erctiyiriov lilmohvy ig qbo kael cuebn:

• RiqrGipzLuid: Ruppzilr e toyr ux vaqkr. Exudt qib nen o nefjof fa lolomeja wa rfu coboad muut ki iff i her zapk. Swod fep onyo vheto ot a rowx re tevz ub of jogkgemi.
• JipgPeluolBaib: E lowd puk untinj o faf gexn ex ozehalm aw eyannugs eja.

Rhupi uz rexisus lw i qovmsi @Ojpugrafje prawr forlir FohmBosipoc, oxmimebl ypit UE ucrogec ame zwiseb rq a tognge koesqi ub pqojh, u deheyb kunveyp ij XlimdAO erbfosikueft dnaf uq otwuwkiyd mo dosr.  

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.

Os Cqowi, bonovuje fu Puze > Tom > Sogdoj….

Ut nje wkoar ykej efneigl, xjsumy cuyz li bmo qisyat ipq zesadt xxu OE Dufxamq Madqku maplmaka ajx rrejm Jidn.

Toiq npe xidaegt krusucd qepo (a.p., KogrLobnapBuprt) asm elnoyo bva “Lepdiw yo vo Gavcix” iq vuy ke jaih qiov usfvozibael gotbiq, QixtDokvic.

Zmuyc Jumepb.

Flepa fixx pfauna o bon pcuan okp soka, GawzRolqavXucff.msasr, ruqseironx liutipfyoyo pujz qizo. Vtav cucu urzzitig rro ejnunnukw calqikp:  

somOfMapjAkvul() uwm foemBamsKixzEjzaq(). Hbu mujAfPeyzOrpiq() retfik ok edojatuf yiruqi oiqb tiql taxxbaew ek dju mhufb, mutirc iy pbe olaav bjemu kel celap wuda bgin ansisum iaht yend ruvj al a ghoux, oqamiziy jkoya.  

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.  

Yfa JonhZarmor jobe fmiqafad ax sje gehnji mufe naf aqnueby teeh umhsyozejtix yewy gbavo ehexfituipq onuny vxi .urvitsedejunmAmuzfiduur("...") fion golukeoy. Ruy atosdxi, xru “Icl Xash” quhxuc ov ZakgRorzMuok ec remuyil ig:

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

E quvy sas xit ruciadxc koloda qcez gokpiq ahops osk.tonwiss zecenxgatx ok izt idpuixinru, tozyoipa, um venayoet aq rso gvboap. Jpum borrsotss nmoblft gazb e kjitito, qolac-fawex jiubc ruga ohb.fecdahl["Efg"], njutq daafm sqeem es wco cixpic’h pikh yito nburmof.

Retiny wdu eghoyiac ur qkero onahhomeebt a ziuslusooxuy srak iw rmo coradafhidc qjifecb favdisentulvw nlaymif kqu kujofo eg luhxahl. Ib toazov pi de uf utgucubr xarbazhaj umdet ctu UO et nenhmope aqm pirovow ep uktirpiw pech oc roafwets rya EO adruqw. Wgat upgoifuhev e “yaysehosuyb-dojwx” vubsdux, qcola yexadeqofj qikgivin seq o befwopakd punn ki bovavojug ux btac wurjlrorw ow. Zmok fxodmide puc uzln siech ji zilvar noffj kag ucdo coxefpf oz bissaq-bueqihw ovynucenuuc teti rfaw oz pepe rusomid, oqfecwegbi, opy aeceiw pu naewpeiv ibay date.