* Cantinho Satkeys

Refresh History
  • j.s.: try65hytr a todos  49E09B4F
    29 de Janeiro de 2026, 21:01
  • FELISCUNHA: ghyt74  pessoal  4tj97u<z
    26 de Janeiro de 2026, 11:00
  • espioca: avast vpn
    26 de Janeiro de 2026, 06:27
  • j.s.: dgtgtr  todos  49E09B4F
    25 de Janeiro de 2026, 15:36
  • Radio TugaNet: Bom Dia Gente Boa
    25 de Janeiro de 2026, 10:18
  • FELISCUNHA: dgtgtr   49E09B4F  e bom fim de semana  4tj97u<z
    24 de Janeiro de 2026, 12:15
  • Cocanate: J]a esta no Forun
    24 de Janeiro de 2026, 01:54
  • Cocanate: Eu tenho
    24 de Janeiro de 2026, 01:46
  • Cocanate: boas minha gente
    24 de Janeiro de 2026, 01:26
  • joca34: BOM DIA AL TEM ESTE CD Star Music - A Minha prima Palmira
    23 de Janeiro de 2026, 15:23
  • joca34: OLA
    23 de Janeiro de 2026, 15:23
  • FELISCUNHA: Bom dia pessoal  4tj97u<z
    23 de Janeiro de 2026, 10:59
  • JPratas: try65hytr Pessoal  4tj97u<z 2dgh8i k7y8j0 classic
    23 de Janeiro de 2026, 05:16
  • j.s.: try65hytr a todos  49E09B4F
    20 de Janeiro de 2026, 18:15
  • FELISCUNHA: ghyt74  pessoal   49E09B4F
    20 de Janeiro de 2026, 11:07
  • j.s.: dgtgtr a todos  49E09B4F
    18 de Janeiro de 2026, 16:02
  • FELISCUNHA: ghyt74   49E09B4F  e bom fim de semana  4tj97u<z
    17 de Janeiro de 2026, 11:18
  • JPratas: try65hytr Pessoal  2dgh8i k7y8j0 yu7gh8
    16 de Janeiro de 2026, 04:50
  • j.s.: try65hytr a todos  49E09B4F 49E09B4F
    15 de Janeiro de 2026, 19:29
  • FELISCUNHA: ghyt74  pessoal   49E09B4F
    15 de Janeiro de 2026, 11:51

Autor Tópico: Practical Test-Driven Development with Xcode and Swift: Write Modularized Code for TDD with XCTest  (Lida 241 vezes)

0 Membros e 1 Visitante estão a ver este tópico.

Offline mitsumi

  • Sub-Administrador
  • ****
  • Mensagens: 129146
  • Karma: +0/-0

Practical Test-Driven Development with Xcode and Swift: Write Modularized Code for TDD with XCTest and UIKit
MP4 | Video: AVC 1280x720 | Audio: AAC 44KHz 2ch | Duration: 50M | 820 MB
Genre: eLearning | Language: English

Write better, more robust, and well-architected code. Then put tests on CI with every run, so you have real proof that your app works as expected. Running tests over and over again costs you very little whereas running manual tests costs time again and again. 100% test coverage is not practical. A more effective approach is to write well-modularized code which is easy to test in isolation with unit tests and then do several integration tests testing the entire flow of your app to make sure all modules work together.
Use XCTest, which Apple provides out of the box with XCode, to test all networking and model layers and plan classes. This is your opportunity to test against several different edge cases since it's easy to simulate different conditions. Unit testing your controllers is complicated because controllers rely on the UIKit controller life cycle that's not available in the test environment. Therefore, it's easier to use UI Testing (also provided by Apple with XCode) to write integration tests. Write a few of them covering your happy paths.

Adding your tests on CI and running them automatically on every commit to your mainline branch will help you avoid timely manual tests or a failing app. Your tests will always be up to date and work for you instead of getting in the way.

Download link:
Só visivel para registados e com resposta ao tópico.

Only visible to registered and with a reply to the topic.

Links are Interchangeable - No Password - Single Extraction