Why test your code ?. Unit Testing: Method for testing individual units (usually a single method) of your app to make sure app si ready to be release.
- 1. Why there are so Many bad apps
- 2. Why test your code?
- 3. Why create Unit Tests?
- 4. Setting up the test Project
- 5. Adding the test code
- 6. Working with the test navigator
- 7. Stepping through the Code
- 8. Deleting and Disabling breakpoints
- 9. Summary
- Undestanding Inheretance
- Overriding Methods
- Overriding Properties
- Prevending Overriding
- Polymorphism
- Summary
- Exercise 15.1
- Solution Movie 15.1
- 1. Creating Initializers for your Custom Classes
- 2. Initialization and Type Inference
- 3. Declaring initializers
- 4. Initializer Parameters
- 5. Designated & Convenience Initializers
- 6. Designated Initializers
- 7. Convenience Initializers
- 8. Initializer Chaining
- 9. Two-Phase Initialization
- 10. Initializer Safety Checks
- 11. Initializer Inheritance
- 12. Overriding Initializers
- 13. Required Initializers
- 14. Optional Properties & Constants
- 15. Failable Initializers
- 16. When to Create Failable Initializers
- 17. Failable Initializer Rules
- 18. The init! Failable Initializer
- 19. Summary
- 1. Targets and Modules
- 2. Access Levels
- 3. Access Control Modifiers
- 4. Types, Members and Access Levels
- Method and Function Access Level
- Initializer Access Level
- Variable, Constant, Property, and Subscript Access Levels
- Getter and Setter Access Levels
- Enumeration Access Level
- Protocol Access Level
- Extension Access Level
- Generics Access Level
- Tuple Access Level
- Nested Type Access Level
- Type Alias Access Level
- 5. Inheritance and Access Control
- 6. The @testable Attribute
- 7. Summary
- An Object's Lifetime
- Memory Management: The Way it was
- Memory Management: The way it is
- Memory Management and Local Variables
- Memory Management and Properties
- Strong Reference Cycles
- Summary
- Exercise 19.1
- Solution Exercise 19.1
See first approach to generics -> Generics
- The Problem with Generalized Code
- A non-generic Solution
- The Generic Method Solution
- Testing the Generic Method
- Declaring Generic Classes
- Testing the Generic Class
- Implementing Other Generic Methods
- Overriding Generic Class Methods
- More Rules of Generics
- Generic Associated Types
- Summary
- Exercise 22.1
- Solution 22.1
- Exercise 22.2
- 1. Using the Target-Action Design Pattern
- 2. Enhancing Your Code with Closures
- 3. Animation Without Closures
- 4. Animation With Closures
- 5. Declaring an Inline Closure
- 6. Benefits of Closures
- 7. Capturing Constants and Variables
- 8. Shorthand Argument Names
- 9. Trailing Closures
- 10. When to Use Closures in Your Apps
- 11. Creating Methods That Accept Closures
- 12. Testing Your Closure
- 13. Passing Closure Algorithms
- 14. Strong Reference Cycles and Closures
- 15. Exercise 23.1
- 16. Solution 23.1