Unit testing_pps
1 like483 views
Unit testing frameworks allow developers to test individual units or components of an application to ensure quality and avoid regressions. The document discusses unit testing and the OCUnit framework for iOS, including its history and how to write tests using asserts. Tests should be written in parallel with code using a test-driven development approach. OCUnit allows automatically running tests that validate the semantics of code.
![Example #import "PersonTestClass.h" #import "Person.h" @implementation PersonTestClass -(void)testCreatePerson { personObj= [[Person alloc] init]; STAssertNotNil (personObj, @"A Person Object was never created"); } @end](https://image.slidesharecdn.com/unittestingpps-111016233114-phpapp01/85/Unit-testing_pps-14-320.jpg)
Unit testing_pps
- 1. Unit Testing framework in iOS
- 2. What? What is Unit-Testing? Available Unit Testing frameworks for iOS. Basics of OCUnit Testing.
- 3. Unit Testing A Paradigm of Test-driven development. Mainly of two types: Logic Unit Testing Testing a smallest logical unit or methods. Application Unit Testing Testing an entire application.
- 4. Unit Testing Frameworks Family of similar frameworks for testing various languages Junit, Nunit, PyUnit etc. OCUnit for Objective-C Ships with MAC OS X developer tools, Included in iPhone sdk 2.2.
- 5. Why? Fewer Bugs More confidence that you’re shipping a high quality product. Find bugs early . Bugs are easier (and cheaper) to fix early in development. Avoid regressions Ensures that changing one piece of code doesn’t breaks another. Document your code
- 6. When and Who? When: Parallel to development. Who: Developer .
- 7. How? Tests are ideally written along with new code (and even before the new code). Test-driven development: Write test first. Fill in the implementation untill test pas. Rinse and repeat.
- 8. Running Unit Tests Automate so you don’t have to explicitly run tests. Many testing frameworks can run tests every time you build. Compiler checks SYNTAX . UnitTest check SEMANTICS
- 9. OCUnit A Unit Testing framework for iOS
- 10. History 1998 - Written by Sen:te. Objective C becomes onr of the first language to benefit from this approach of testing. 2002 –Presented at WWDC. 2005 – Apple decided to integrate it in Xcode 2.1. 2008 – Apple actually integrated OCUnit in iPhone sdk 2.2
- 11. SenTestCases is abstract test superclass Automatically runs methods thath begin with “test” Macros for asserting conditions during tests. OCUnit
- 12. Asserts Macros
- 13. Example #import <SenTestingKit/SenTestingKit.h> #import <UIKit/UIKit.h> @class Person; @interface Person TestClass : SenTestCase { Person *personObj; //create the reference of the class to be tested } @end
- 14. Example #import "PersonTestClass.h" #import "Person.h" @implementation PersonTestClass -(void)testCreatePerson { personObj= [[Person alloc] init]; STAssertNotNil (personObj, @"A Person Object was never created"); } @end
- 15. DEMO A Unit Testing framework for iOS