Starting 13 test scenarios

If you have Siri on your phone Siri’s voice will pronounce the phrases.

VSSpeechSynthesizer could be found in XCode 4.4 in iOS PrivateFrameworks

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.1.sdk/System/Library/PrivateFrameworks/VoiceServices.framework
 
Add new VSSpeechSynthesizer.h:

// VSSpeechSynthesizer.h
@interface VSSpeechSynthesizer : NSObject {}
+ (id)availableLanguageCodes;
+ (BOOL)isSystemSpeaking;
- (id)startSpeakingString:(id)string;
- (id)startSpeakingString:(id)string toURL:(id)url;
- (id)startSpeakingString:(id)string toURL:(id)url withLanguageCode:(id)code;
- (float)rate;              // default rate: 1
- (id)setRate:(float)rate;
- (float)pitch;             // default pitch: 0.5
- (id)setPitch:(float)pitch;
- (float)volume;            // default volume: 0.8
- (id)setVolume:(float)volume;
@end

Add to your EXTestController.m

VSSpeechSynthesizer *synthesizer;

- (void)initializeScenarios {
    ...
    synthesizer = [VSSpeechSynthesizer new];
}

- (void)startTestingWithCompletionBlock:(KIFTestControllerCompletionBlock)inCompletionBlock {
    [synthesizer startSpeakingString:@"starting testing"];
    ...
}

Next if you like your test to speak on iOS Simulator too you can add this implementation of
VSSpeechSynthesizer

#import "VSSpeechSynthesizer.h"

#if TARGET_IPHONE_SIMULATOR

@implementation VSSpeechSynthesizer
+ (id)availableLanguageCodes {
    return nil;
}
+ (BOOL)isSystemSpeaking {
    return NO;
}

-(NSString *)selectVoiceForPhrase:(NSString *)phrase {
    NSDictionary *keywordToVoice = @{
    @"failures!" : @"Bad",
    @"failure!" : @"Bruce",
    @"FAIL" : @"Agnes"
    };
    NSString *keyword = nil;
    for (keyword in [keywordToVoice allKeys]) {
        BOOL found = NSNotFound != [phrase rangeOfString:keyword].location;
        if (found) {
            break;
        }
    }
    return keyword ? [keywordToVoice objectForKey:keyword] : @"Vicki -r 150";
}

- (id)startSpeakingString:(id)what {
    NSString *voice = [self selectVoiceForPhrase:what];
    NSString *command = [NSString stringWithFormat:@"say -v %@ %@", voice, what];
    system([command cStringUsingEncoding:NSASCIIStringEncoding]);
    DLogObject(what);
    return nil;
}
- (id)startSpeakingString:(id)string toURL:(id)url {
    return nil;
}
- (id)startSpeakingString:(id)string toURL:(id)url withLanguageCode:(id)code {
    return nil;
}
- (float)rate {
    return 1;
}
- (id)setRate:(float)rate {
    return nil;
}
- (float)pitch {
    return 0.5;
}
- (id)setPitch:(float)pitch {
    return nil;
}
- (float)volume {
    return 0.8;
}
- (id)setVolume:(float)volume {
    return nil;
}
@end
#endif

Hear the sound of all tests passed.

All 13 Tests Passed

Next we added an announcement of the first failure in the test suite to help us debug the issue. That announcement comes from a voice called “bad news” logically. See more voices available on Mac OS X System Preferences Speech panel:

Custom Font Support
Applications that want to use custom fonts can now include those fonts in their application bundle and register those fonts with the system by including the UIAppFonts key in their Info.plist file. The value of this key is an array of strings identifying the font files in the application’s bundle. When the system sees the key, it loads the specified fonts and makes them available to the application.

For more information about the keys you can include in your application’s Info.plist file, see Information Property List Key Reference.

Here at Blazing Cloud we are happy to announce the launch of our first official product, BieberFy! BieberFy was inspired by Justin Bieber and the overwhelming response to his floppy teenage hair cut. So we thought, what would be better then to make an app that could give anyone Justin Bieber’s hair du? I mean, haven’t you always wondered what you would look like with Justin Bieber’s hair? Okay, maybe thats a stretch, wondering what you would look like with Justin Biebers likeness and all, but if  your curiosity gets the better of you there IS an app for that now.

BieberFy is an application that runs on iOS 4 for the iPhone and iPod touch. BieberFy takes advantage of the devices built in camera by displaying an overlay that gives you three Justin Bieber hair styles to choose from.  The initial version of the app allows you to take a photo with one of the hair styles, preview it and if you choose to accept, it will save it to the device’s built in photo album.

BieberFy is available for sale world wide via the iTunes app store for $0.99.

We hope you have just as much fun with this app as we do!

After poking around a bit, it seemed that the @-webkit-keyframes styles in jqtouch.css defined for the sliding transitions were being applied in parallel when running in Android 2.0. For example, a slide-in-from-right link  has these webkit animated styles applied to it:

.in, .out {
    -webkit-animation-timing-function: ease-in-out;
    -webkit-animation-duration: 350ms;
}

.slide.in {
    -webkit-animation-name: slideinfromright;
}

@-webkit-keyframes slideinfromright {
    from { -webkit-transform: translateX(100%); }
    to { -webkit-transform: translateX(0); }
}

On  iPhone and Android 1.0 devices,  a slide-in-from-right screen slides in correctly from 100% to 0 in about 350ms. But on Android 2.0 devices,  the screen appears immediately as if no animation occurred.

To work around this problem,  you have to manually set the start position first, then the end position and animation style. That is, instead of letting the @-webkit-keyframes do the work, you have to manually position the screen at 100%, then set the animation and final position style after a small time interval. For example, the key portion of the code to consider  is:

toPage.css("webkitTransform", "translate3d(100%,0px,0px)");
setTimeout(function() {
    toPage.css({webkitTransitionDuration: "350ms",
    webkitTransitionTimingFunction: "ease-in-out"});
    toPage.css("webkitTransform", "translate3d(0px,0px,0px)");
}, 5);

Note that we first set the starting position then wait about 5 milliseconds before applying the animated style (webkitTransitionDuration and webkitTransitionTimingFunction). After the transition completes, I clear the style from the page:

toPage.css({webkitTransitionDuration: null,
            webkitTransitionTimingFunction: null})

The sliding animation is handled in the animatePages function. Here’s the code with workaround (my changes in bold):

function animatePages(fromPage, toPage, animation, backwards) {
    // Error check for target page
    if(toPage.length === 0){
        $.fn.unselect();
        console.error('Target element is missing.');
        return false;
    }

    // Collapse the keyboard
    $(':focus').blur();

    // Make sure we are scrolled up to hide location bar
    scrollTo(0, 0);

    // Define callback to run after animation completes
    var callback = function(event){

        if (animation)
        {
            if (animation.name == "slide") {
                var css = {webkitTransitionDuration: null,
                    webkitTransitionTimingFunction: null};
                toPage.css(css);
                fromPage.css(css);
            }
            toPage.removeClass('in reverse ' + animation.name);
            fromPage.removeClass('current out reverse ' + animation.name);
        }
        else
        {
            fromPage.removeClass('current');
        }

        toPage.trigger('pageAnimationEnd', { direction: 'in' });
        fromPage.trigger('pageAnimationEnd', { direction: 'out' });

        clearInterval(dumbLoop);
        currentPage = toPage;
        location.hash = currentPage.attr('id');
        dumbLoopStart();

        var $originallink = toPage.data('referrer');
        if ($originallink) {
            $originallink.unselect();
        }
        lastAnimationTime = (new Date()).getTime();
        tapReady = true;
    }

    fromPage.trigger('pageAnimationStart', { direction: 'out' });
    toPage.trigger('pageAnimationStart', { direction: 'in' });

    if ($.support.WebKitAnimationEvent &&
        animation &&
        jQTSettings.useAnimations) {
        tapReady = false;
        if (animation.name == "slide") {
            toPage.one('webkitTransitionEnd', callback);
            toPage.addClass('in current');
            fromPage.addClass('out');
            toPage.css("webkitTransform", 
                       "translate3d(" + (backwards ? "-100%" : "100%") + ",0px,0px)");
            fromPage.css("webkitTransform", 
                         "translate3d(0px,0px,0px)");
            setTimeout(function() {
                var css = {webkitTransitionDuration: "350ms",
                    webkitTransitionTimingFunction: "ease-in-out"};
                toPage.css(css);
                fromPage.css(css);
                toPage.css("webkitTransform",
                           "translate3d(0px,0px,0px)");
                fromPage.css("webkitTransform",
                             "translate3d(" + (backwards ? "100%" : "-100%") + ",0px,0px)");
            }, 5);
        } else {
            toPage.one('webkitAnimationEnd', callback);
            toPage.addClass(animation.name + ' in current ' + (backwards ? ' reverse' : ''));
            fromPage.addClass(animation.name + ' out' + (backwards ? ' reverse' : ''));
        }
    } else {
        toPage.addClass('current');
        callback();
    }

    return true;
}

Note that jQTouch sets $.support.WebKitAnimationEvent to false for Android 2.0 devices even though it does support WebKit animation. Make sure you set that to true. Replace the animatePage function in your jQtouch with the function in this post and now  you should be golden with iPhone and Android!

double myDouble = 2.2;
NSLog(@"myDouble %f", myDouble);

[self testDouble:myDouble];

- (void) testDouble:(double)myDouble {
    NSLog(@"testDouble %f", myDouble);
}

This code prints:
myDouble 2.200000
testDouble 2.200000

No surprises there. But the same code using a float behaves very strangely:

float myFloat = 3.3;
NSLog(@"myFloat %f", myFloat);

[self testFloat:myFloat];

- (void) testFloat:(float)myFloat {
    NSLog(@"testFloat %f", myFloat);
}

This code prints
myFloat 3.300000
testFloat 36893488147419103232.000000

So what happens to the float that is passed to the testFloat method? According to this Techtopia article about Objective-C 2.0 Data Types when you create a float like this:

float myFloat = 3.3;

It is internally stored as a double, which has greater precision. If you actually want to store something as a float you need to append an “f” to the number like this:

float myFloat = 3.3f;

So I thought perhaps that was the problem – that internally it was represented as a double, so when passed in to a method expecting a float there was a conversion error. But when I modified the code above to include the “f” I get the same result.

I also get the same result when I pass the float in directly to the method like this:

[self testFloat:3.3f];

So what the heck is going on here? Why can’t I pass a float to a method? What am I missing? I’ll follow up with a comment when I figure it out, but does anybody know why this is happening?

double myDouble = 2.2;
NSLog(@"myDouble %f", myDouble);

[self testDouble:myDouble];

- (void) testDouble:(double)myDouble {
    NSLog(@"testDouble %f", myDouble);
}

This code prints:
myDouble 2.200000
testDouble 2.200000

No surprises there. But the same code using a float behaves very strangely:

float myFloat = 3.3;
NSLog(@"myFloat %f", myFloat);

[self testFloat:myFloat];

- (void) testFloat:(float)myFloat {
    NSLog(@"testFloat %f", myFloat);
}

This code prints
myFloat 3.300000
testFloat 36893488147419103232.000000

So what happens to the float that is passed to the testFloat method? According to this Techtopia article about Objective-C 2.0 Data Types when you create a float like this:

float myFloat = 3.3;

It is internally stored as a double, which has greater precision. If you actually want to store something as a float you need to append an “f” to the number like this:

float myFloat = 3.3f;

So I thought perhaps that was the problem – that internally it was represented as a double, so when passed in to a method expecting a float there was a conversion error. But when I modified the code above to include the “f” I get the same result.

I also get the same result when I pass the float in directly to the method like this:

[self testFloat:3.3f];

So what the heck is going on here? Why can’t I pass a float to a method? What am I missing? I’ll follow up with a comment when I figure it out, but does anybody know why this is happening?

iBooks

In the first 65 days users have download over 5 million books

Enhancement to iBooks

Highlight sections
Make notes
Bookmark the page in the corner
View and read PDFs

AppStore

Apple supports two platforms, HTML5 and AppStore (225,000 apps)
15,000 apps submitted every week supporting up to 30 languages
95% of apps are approved in 7 days
5% of apps get rejected

Reason why apps are rejected from the AppStore

Use of private Apple APIs
App doesn’t work like developer says it works
The app crashes

Downloads from the AppStore total 5 billion
$1 billion dollars have been paid out to developers thus far

iPhone stats

Us smartphone market share Q1 of 2010

RIM 35%
iPhone 28%
Winmo 19%
Android 9%
Other 9%

US mobile browsers share Q1 of 2010

iPhone 58.2%
Android 22.7%
Rim 12.7%
Other 6.4%

iPhone 4

1st new feature

All new design
9.3 mm thick
“Thinnest smartphone on the planet”
Camera and LED flash
2nd mic for noise cancellation
Integrated Antennas in the structure of the phone
Stainless steel body
Glass on front and back

2nd new feature

Retina display
4 times as many pixels in the same area
326 pixels per inch
300 pixels per inch is the limit of the human retina to differentiate pixels
3.5 inches 960×640
800:1 contrast ratio
IPS technology
78% of the pixels on the iPad on the iPhone

3rd new featured

Powered by the A4 processor
3G talk time equals 7 hours
3G browsing time equals 6 hours
WIFI browsing time equals 10hours
32G and 16G storage options

4th new feature

3 Axis Gyroscope
Pitch, roll and yaw
Rotation about gravity
Gyro plus accelerometer provides 6 axis

5th new feature

New camera system
5megapixel sensor
Backside illuminated sensor
5x digital zoom
LED flash built in
HD video recording 720p at 30 frames per sec
Built in video editing (iMovie application)
LED flash will stay on for video

6th new feature

Renaming iPhone OS to iOS 4
1500 new developer APIs
100 new user features
Multitasking
Folders
Added bing as a search option (with google and yahoo)

Golden master candidate released June 7th

100th million iOS device (iPhone + ipads + iPods) sold

7th new feature

iBooks coming to iPhone
Same features as the iPad
Wireless sync between iPhone, iPad and iPod touch
Same books for all devices at no extra charge

150 million accounts with credit cards (iBook store, AppStore and iTunes Store)
Over 16 billion downloads from all three stores

8th new feature

iADs
Ads keep you in your app which gives a better user experience
Built right into iOS4
Brands so far to sign up (within the last 8 weeks): Nissan, Citi, unilever, AT&T, Chenel, GE, liberty mutual, State Farm, Gieco, Cambell, Sears, JCPennys, Target, Best Buy, DirecTV, tbs, and Disney

These companies committed 60 million dollars towards iAds

9th new feature

FaceTime video calling
Uses wifi, no setup required
Use front or rear camera
Wifi only in 2010 have to work with the cellular companies to get their networks ready for video calling

Price and availability

2 colors white or black
$299 for 32 gig $199 for 16 gig
On sale June 24th
Pre-sale June 15th

iOS 4 upgrades are free for everyone (iPhone + iPod Touch)!!!

Here at Blazing Cloud we really like Test-Driven Development (TDD). We try to use it for all of our development projects, and we recently learned how to do it for IPhone development.

The unit test tool available for Cocoa development is more like JUnit for Java than RSpec for Ruby. Each test is implemented as a method, and it is described by its method name, so you need to get creative with camel case. In addition, the error messages that you get out of the c compiler are difficult to parse (at least to those of us with limited c experience), which makes the watch it fail first and then fix it methodology difficult. However, it is still worth suffering in the unfriendly environment to get the benefits of a full test suite. Hopefully the knowledge that we gained in muddling through this will help you get started in your own project.

There are two types of tests suites for IPhone development: Logic Tests and Application Tests.

• Logic Tests test business logic and are run independently of any device (including the emulator).
• Application Tests test the UI and everything that can only be tested on the device.

This article will detail how to develop business logic code using Logic Tests. We will follow up with Application Testing in a subsequent article. The Apple developer site has documentation for Unit Testing Applications, and you may want to read this document first. We will walk through the set-up in this article but if you need more detail you may find it in the Apple site.

Logic Testing

We will now demonstrate Logic Testing using a simple tip calculator as an example. To begin (with iPhone SDK and Xcode installed) launch XCode and create a new View Based IPhone Application called TipCalc. As a sanity check you can try to run this empty app in the simulator and you will see an empty view screen.

Make a new target for your logic tests. Right click Targets and select Add -> New Target. Select Unit Test Bundle and name the bundle “Logic Tests”. You can close the little info window that comes up, and you will see your new target in the Targets group.

Create a new group under the TipCalc main group called “LogicTests”. This will look like a directory under your TipCalc application as shown here:

Add a new file to the LogicTests group that is of type Objective-C test case class and call it “TipCalcTests.m”. Make sure the box is checked to create the associated header (.h) file, and select only the Logic Tests target to add the new file to. When you hit Finish the two new files will be added.

At this point you should try to run your tests. Make Logic Tests your active target and click Build and Run. You won’t really see anything happen when you do this, but look in the lower right corner of your XCode window:

Click on the red error icon to open up the build results window. The errors you see won’t really make any sense at this point, and I think its because they are generated during the run step and this target doesn’t have an executable to run. If you click Build instead of Build and Run you will get a more informative error. You don’t actually have to run anything because the tests are executed during the build step.

The new error should look like this:

This error is happening because when you create a new test case file by default it is set up to be an Application test, not a Logic test, so it expects to find an ApplicationDelegate instance, which is only present in the running app. You can remove the code that is for application testing from these test files, as you will make separate test files for those tests. In your header file remove these lines:

//  Application unit tests contain unit test code that must be injected into an application to run correctly.
//  Define USE_APPLICATION_UNIT_TEST to 0 if the unit test code is designed to be linked into an independent test executable.

#define USE_APPLICATION_UNIT_TEST 1

and these lines:

#if USE_APPLICATION_UNIT_TEST
- (void) testAppDelegate;       // simple test on application
#else
- (void) testMath;              // simple standalone test
#endif

so that you just have an empty header file. From the implementation file you can remove these lines:

#if USE_APPLICATION_UNIT_TEST     // all code under test is in the iPhone Application

- (void) testAppDelegate {
    
    id yourApplicationDelegate = [[UIApplication sharedApplication] delegate];
    STAssertNotNil(yourApplicationDelegate, @"UIApplication failed to find the AppDelegate");
    
}

#else                           // all code under test must be linked into the Unit Test bundle

- (void) testMath {
    
    STAssertTrue((1+1)==2, @"Compiler isn't feeling well today :-(" );
    
}
#endif

so you have an empty implementation file. Now if you hit Build again you will not have any errors, and we can start writing some tests.

In the spirit of TDD we will write a test first before we write any other code. Add the following code to your implementation file:

- (void) testTipCalculation {
    
    float percentage = .20;
    float bill = 34.45;
    float expectedTotal = percentage * bill;
    NSLog(@"expected total: %f", expectedTotal);
    float result = [TipCalculator calculateTipFor:bill andPercentage:percentage];
    
    STAssertEquals(expectedTotal, result, @"Tip not calculated correctly. Expected %f but got %f", expectedTotal, result);
}

and the corresponding declaration in your header file:

@interface TipCalcTests : SenTestCase {

}

- (void) testTipCalculation;

@end

Build again and you will get a useful error: “‘TipCalculator’ undeclared (first use in this function)” because we haven’t defined the TipCalculator class. Add the TipCalculator class to the Classes group and add it to both the TipCalc and Logic Tests targets. Edit TipCalcTests.h and import TipCalculator.h like so:

#import "TipCalculator.h"

Run your tests again and you will see the following results:

As you can see, the error message isn’t particularly helpful, but there is a warning that tells us “‘TipCalculator’ may not respond to ‘+calculateTipFor:andPercentage:’”

Add the method declaration now to your TipCalculator header:

+ (float)calculateTipFor:(float)bill andPercentage:(float)percentage;

and a stub for the method in your implementation file that returns a hard coded value:

+ (float)calculateTipFor:(float)bill andPercentage:(float)percentage {
	return 0.8;
}

Now when you build you will get a useful error telling you that your test failed:

Notice that the only thing that it prints out is the error message you specifically told it to generate including the expected and actual values. So you will need to make sure your test results statements are meaningful.

If you run into issues it might be useful to log things to the console. In the sample code there is an NSLog statement:

NSLog(@"expected total: %f", expectedTotal);

This output doesn’t get written to the run console in XCode (maybe because the tests are executed during the build step, not the run step?) but it does get written to the system console. You can find the system console by typing “console” into spotlight. The system console looks like this:

A lot of messages get printed here, but if you filter the list by the string “otest” you will see your messages. If anyone knows how to get log output to show up in XCode please leave us a comment.

If you do want to launch your app in the simulator every time you run your tests you can just drag you TipCalc target into your Logic Tests target and click Build and Run instead of Build.

So that’s basically it, now you know how to write Logic Tests. You can find a complete list of test macro functions (like STAssertEquals) in the Unit-Test Result Macro Reference in the Apple site.