Some tests with caveat

[kaiwu]

Hi,

I've added a few more tests with caveat:

• the latest addition of Mutable variants break a few existing tests,
  as you might have noticed, which i don't understand

• there seems to have no way of verifying weak reference in iOS ?

  [self weaklyAssociateValue:subject withKey:&kAssociationKey];
  #if BK_HAS_APPKIT
  //zeroing weak reference is not available for iOS
  NSString *associated = (NSString *)[self associatedValueForKey:&kAssociationKey];
  GHAssertNil(associated,@"associated value is nil");
  #endif
  

• for the other BlocksKit category on UIView classes, is there a way to simulate the tap events ?
  i have googled a while and cannot find good solutions, so the test does not really cover the block part yet

[zwaldowski]

Yeah, I fixed the mutable tests thing. I thought the runtime differentiated selectors by return type... e.g., (NSArray *)select would not be overridden by (void)select. That's not true, and it's fixed. I'll merge this in a few minutes.

As far as simulating taps, I know there's something that Three20 did to unit test, but it's a very very private method.

Additionally, weaklyAssociateValue:withKey: does not use a weak reference on any version of iOS. It's too late to change it now, but it really just associates objects with OBJC_ASSOCIATION_ASSIGN. I'll look into doing a weak reference, though.

[zwaldowski]

Actually, Apple gives us UI testing features:

• https://developer.apple.com/library/ios/#documentation/DeveloperTools/Reference/UIAutomationRef/_index.html#//apple_ref/doc/uid/TP40009771
• http://alexvollmer.com/posts/2010/07/03/working-with-uiautomation/

No, I don't know how to implement it. :-D

[kaiwu]

the UI automation looks not very easy ...
i will implement a few basic tests (leaving the block) for the time being

close this pull request and replace this with a new one