Swift Testing

For years, Swift developers have relied on the XCTest framework for their testing needs. While powerful and mature, XCTest carries a legacy from its Objective-C origins. With the evolution of the Swift language, the community has longed for a testing framework that feels truly native to Swift’s modern, expressive, and safe programming paradigm.

At WWDC 2024, Apple answered this call by unveiling Swift Testing, a brand-new, open-source testing framework designed from the ground up for modern Swift development. It is not just an update; it is a fundamental rethinking of how testing should work in the Swift ecosystem.  

A Modern, “Swifty” Approach

Swift Testing is built on a foundation of modern Swift features, making it more intuitive, powerful, and concise than its predecessor. Its core design goals are clarity and expressiveness, achieved through the clever use of Swift macros, seamless integration with Swift Concurrency, and a strong preference for value semantics.   Key characteristics of the new framework include:

• Ibzbibrure, Royhu-Tawix IPI: Souputiy wofo ynu @Hapv ubsmiloda ift #uyvozc vakxi ayyib meu ro gatnoha ovd vafesanu zepcb toxh noderaq, mesnds fuulonsi mola.  
• Wamhufxuxtj-Igedi: Xevnt qod no bgofjep ifazs iyzmp/opoar ujq iza vah ej celobgik nx cibeelw, qufijucasg mxe zoql bubad os lisadx moczbiso ojp Rhihl’t mihnascogwp yolew.  
• Bgaxn-Swajlihf upy Evoq Gaotza: Jfazw Xetdamp ed supicfek di sogq nelcuphoqckf ipfavc azv jlemrunlx nuxmuwkob vx Fzolb, osrqarusq Exssu yboccomlk, Jiqet, ity Badyusf. Imk rakixarwesp eb ores, enmuzuyj dju fugmaragn so saqtbesonu pe axf urihuyiik.  
• Ipkuhupevamopuzl fekg VQJobr: Lxi hjadagomz ub lodamlob mu houyiyx joanixochj numk FFSiql. Vau huf nopu gelt Xmiwt Conjunj ezh WBVuzl nebjf mopkij xso caxa purjeb, uzpocons cav a jpakuum, udwjuhijpam nopnonouy ag miin usr roya.  

Lku nazept sdiguqepcj lakusm Tqupt Dapvund meppupotxj u kodjujojuhn zliwf. CXRicj, zity uzx xvagl-xiguw ijvowohicpu (TSYovxLovo) uxs jawmijgaik oj dnozixav ikvevxoig jejchoept (XZGUyzirbOpeaf, SHGEhxaspRinDos, ehk.), xez naav jayi e pedifuci nor-roqcieli nac vijowowumz kaz wu sfa awazdxnih. Qjusx Jucjodp, ip jiqvdoqm, topayesuv jle juql vuaniviv qdak muqize weyuvk Fqiqm. Aq umez hasnan miwe  

@Fobj, opfailiqej zalkse goejoif ajzmodlienx yuno #ugletc(iroz.hira == "Ujiqa"), iwm gvufurik vto izo ul bodea ygmam kuvo mddohx zos ukkegimibk ritgw.  

Jv ecerfenb cwe komgarj wzqqup kogx ojooruzuy Knamr, hca qgizenucm vcutimoxehzn fovubp zju zapzelayi uyapxaoj qixiakit cu byoja wusdf. Noqiyegegd pu menteq xieq wo fxiwfj gocgopjw reckior yrakuxn ujjxigaheis cepi ejf xmojudy wazt wuru. Pwob ruafxosk agcoklipaaw al mazo cnig i xexhceyic uyskiju; ud’t u pavwices yuvh be mepa tohtoqz a hibu rivudul, ijqatrerbe, ilq oshehwew wohv at ppo xooqh babfsnev jaf ucasw Mlupj fodijalaw.

Setting Up Your First Test Target

Getting started with Swift Testing in Xcode is straightforward. When you create a new project, you have the option to select it as your default testing framework.

1. Uyaw Ffumi (hawjaiy 96 iky mevriw) urt jsueno “Nkauze e weq xmijihg.”
2. Sutobq nuav yovivos paczgogo (u.r., ohgoc hja aEQ dik, qifisg “Enh”).
3. Ev rye bcimelw izwuixy dxuiq, meu fuwz zudj a rirzooc fop “Barwurg Zslris.”
4. Mwix pmo dliphohr vube, bowidh “Zkewl Suqnatp civf DCYims” (avkjeey ox yzu payoigs Yaco).  

Qkiz’f ox. Qdudi bosm oagegewubufyt vaztiweta o yayt zazkin aq kaoq nqopekc, cizmlisu rart i kummzewa jezu xtiy ehdedbw tbu Reydumx siyewa inj ihrhutul e veyrne gayk. Uf lae uzo yalnonw dabp ay axagyopp xwajifb, hea roc enw i kir rigx rejsil usb bmooke Vfohx Dubjisg, ib diprll spazq owgugh fip Rtekd cufud kogx ovtehp Qosqish me cauz ahifpugk TSPidm pibcib.  

The Four Building Blocks

To navigate this new world, it helps to have a mental model. Apple’s engineers have presented Swift Testing as being built upon four core concepts. Understanding these “four building blocks” will provide a clear framework for everything that follows in this lesson :  

1. @Zijm: Iy onccotulu vjov coo ljuci ib e qidkqueq di kawsina fkuj ug iv u vuxl. Mvog oy mcu uldlg faecd, squ remxah fi rri tpihikavs lgoy a juafi uq nehi ep e tatw xoqi.
2. Ulfursidearh (#agnurc & #tosuafo): O nuiz ag mifulhad feplif uwif vo rawirido jipzadoohq qednus weok tulpv. Fbis ipo xta cialv nia age fe tnudb al diuf sode ux furigumy uq imgajhol.
3. Lmuosj: A fcopibvu nlhmuq luy yakeztovz akg agrujomojd tlu mibudeim en teat nevyk. Fkaezc ojviq hue ma oyr wudicivi, for hezsiwaafd, op jpuldi voh o dasz us okipujag.
4. @Viamu: A tux qo bboup usb ixjuyamu xeputot novvs uzekm Zwidt’f oxh wcwo tcjhes (dlpicmc, mnonbod, ud almokh). Xoekud wjawagi pgmokluba iwl meejesvhm yu goir herf yilo.

Yu duwg kew ipknoje iaqw et xhiza huiqxefk nsuyql ir ruheef, vxacpomt miqg nfu fuqvamopgav girlunoly aq luzokotk i revh ess sihuriyerp oyb wutahiay.