Please enable JavaScript.

Coggle requires JavaScript to display documents.

Testing blogpost (Structure (Designing test cases (TDD skip this section?…

- - - - When is our job really done?
        
        Add Hillel tweet here
        
        Keychain
        
        Api error
      - Speed
        
        Wouldn't be nice if I fire the simulator once and have high hopes it works?
        Can I fully develop the model, the view model, the business rules, catering them for all their edge cases (Api 401, keychain failure, user defaults interaction) without spinning up the simulator one or two times?
        Without even having implemented the navigation to my screen?
        
        To me this one is one of the greatest joys of testing.
        Usually people claim that testing slows you down while developing but speed you up later when you make changes.
        I have seen many cases were testing really speeds up the process well developing
    - - Really tied to the above argument.
        Refactoring Is only true to its meaning when you have tests to point out things broken.
        Otherwise it is rewriting with the risks it holds. I made it nicer, but did I break something?
    - - Common argument in favour of testing.
        Tests act as a safety net.
        A failure in our app could be very costly.
        Increase trust that we can add new code and modify existing without breaking something.
        Remove fear from older and newer member sof our team of touching green field areas.
  - - - Direct indirect Inputs/outputs
        
        Test doubles
        
        Controlling Indirect inputs/outputs
        
        Show small example of finding dependencies and pulling them out to control them
        
        Meanings
    - - In the mobile landscape it seemed as testing came second - it is not like the testing mindset is embedded in our framework
      - Common arguments in the past were the simplicity of the domain but mostly the lack of knowledge
      - Common questions arise all at once, that are not so easy to answer in the beginning?
        How do I test my existing code?
        How do I test new code?
        What is dependency injection? Do I need it to write tests?
        What do I do with things like the Network Client, the userDefaults. or a socket client?
        What tests do I write? Man this still is a struggle :)
        "All these could pop up all these in the following sections"
        Can often lead to disappointment and abandon testing as being something with a high entry barrier.
  - - - Spy, stub or mock?
      - Sourecery
    - - Read write reflection
  - - - You get all these for free -
        the tests are created along with the code
        
        See Kent Beck’s book
    - - The functions and their inputs area are huge 😞
  - - - Unit Tests
      - Characterization Tests
      - Snapshot Tests
      - End 2 End Tests
      - Our main focus was and still is Unit Tests