Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Tests

 Tests

1- definitions
2- tools
3- iOS frameworks

Thibaut Coutard

February 10, 2020
Tweet

More Decks by Thibaut Coutard

Other Decks in Programming

Transcript

  1. Why ? • More stable applications • Less bugs •

    More confidence • Use it as documentation
  2. Unit Test • Individual test • Unit smallest part of

    the system • Simplest way to test • Lowest cost • Few seconds
  3. Integration Test • Interaction between components • At least two

    or more components • Less tests than UT • Relatively low cost • Seconds/Minutes
  4. UI Test • Test the whole system • Still automated

    • Harder to test • Still cheaper than manually • Minutes/Hours
  5. Manual Test • Test the whole system • Hard to

    test all cases • Very Expensive • Hours/Days
  6. BDD • Gherkin : Given/When/Then • Understandable by everyone •

    Speaks about the user behavior and not the technical behavior • Written with both product, development teams and customer
  7. Quick • BDD framework for swift and objective-c • Can

    be written using the specifications • Easier to read and write
  8. OHHttpStub • Stub HTTP calls for the whole app •

    Helps test API wrappers • Can simulate bad/no network
  9. Resources • Test Driven iOS Development with Swift 4 •

    https://github.com/kif-framework/KIF • https://github.com/Quick/Nimble • https://github.com/Quick/Quick • https://github.com/AliSoftware/OHHTTPStubs