Please merge this account with user 742512

Sep
24
awarded Autobiographer
Sep
24
awarded Autobiographer
Sep
24
awarded Autobiographer
Aug
27
comment Creating mock cloud kit objects for unit testing
After a quick look it seems like a MockProtocolExtension is totally doable if not completely insane. A lot of extra boiler plate. In the midst of this code I've realized that since CKDatabase takes so many completionHandlers: I could just have these completion handlers be methods of my class (somehow) and call these methods with my unit tests. I'd never mock CKDatabase but I would call the completion handlers/methods in my unit tests making sure I aped all the possible returns I could get from CKDatabase.
Aug
27
comment Creating mock cloud kit objects for unit testing
My newest thought is to create an protocol extension of CKDatabase with my own wrapper methods to CKDatabase methods. Since my object would be a Protocol instance of unknown class type I could then mock an object of that protocol. Phew. Maybe to much spaghetti here.
Aug
27
comment Creating mock cloud kit objects for unit testing
Thanks. I'll check that out. I'm assuming then you don't do unit testing for the Cloud Kit portion in that framework but mock your DAO object only.
Aug
25
asked Creating mock cloud kit objects for unit testing
Jun
18
comment Swift to Objective-C header not created in Xcode 6
I seemed to have followed these 2 steps and still seem to be having issues. I'll try starting a new project without the space in the name and see if i can get it to work.
Jun
13
comment Do you have to bridge to ObjectiveC for float in swift?
That's fine (Float 32 and Double 64). But never had to deal with this problem in Objective C for some reason.
Jun
13
comment Do you have to bridge to ObjectiveC for float in swift?
Appears to be related to whether the target is 64 bit or 32 bit
Jun
13
asked Do you have to bridge to ObjectiveC for float in swift?
Jun
12
awarded Scholar
Jun
12
accepted Swift Optional values out of an NSSet
Jun
12
asked Swift Optional values out of an NSSet
Nov
30
awarded Necromancer
May
24
answered NSLayoutConstraint constraintWithVisualFormat can't reference superView
May
23
comment iPhone app opens on iPad like an iPad app
Talked to a friend at NSCoders. He thinks it might be the project file that got screwed up when merging from an old repo. Maybe the interface is saying iPhone but the compile settings are actually iPad/iPhone. Really strange. The app opens in the iPad as an iPhone app at first. it has the weird beveled border around it at a small size and then as soon as my main view controller gets loaded the app goes full screen.
May
5
comment NSLayoutConstraint constraintWithVisualFormat can't reference superView
Self is blue outlined box. It's one view with border.
May
5
revised NSLayoutConstraint constraintWithVisualFormat can't reference superView
added 123 characters in body
May
5
comment NSLayoutConstraint constraintWithVisualFormat can't reference superView
Yup containing view is the green background blue outline view. Something is wrong with that view. It's set up in IB. I'll add images.
1 2 3