Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8140583
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T12:12:38+00:00 2026-06-06T12:12:38+00:00

I’m parsing some json to return a basic string token or error message. –

  • 0

I’m parsing some json to return a basic string token or error message.

- (void)callBackWithVerifyHttpResponse:(NSData *)response
{
    SomeResult *result = [self.parser parseVerifyHttpResponseAndReturnResult:response];
    if (result.token) { [self.delegate callBackWithToken:result.token]; }
    if (result.error) { [self.delegate callBackWithError:result.error]; }
}

The tests that prove this

- (void)testVerifyCallbackInvokesErrorCallbackOnDelegateWhenParserReturnsError
{
    SomeResult *result = [[SomeResult alloc] init];
    result.error = @"fail";
    [[self.delegate expect] callBackWithError:@"fail"];
    [[self.delegate reject] callBackWithToken:OCMArg.any];
    [[[self.parser stub] andReturn:result] parseVerifyHttpResponseAndReturnResult:nil];
    [self.sut callBackWithVerifyHttpResponse:nil];
    [self.delegate verify];
}

- (void)testVerifyCallbackInvokesTokenCallbackOnDelegateWhenParserReturnsToken
{
    SomeResult *result = [[SomeResult alloc] init];
    result.token = @"token";
    [[self.delegate expect] callBackWithToken:@"token"];
    [[self.delegate reject] callBackWithError:OCMArg.any];
    [[[self.parser stub] andReturn:result] parseVerifyHttpResponseAndReturnResult:nil];
    [self.sut callBackWithVerifyHttpResponse:nil];
    [self.delegate verify];
}

All was well until I wired this up to an actual endpoint -only to find that unless I modified the callback like the below -it was calling both callbacks (not what I was hoping for)

- (void)callBackWithVerifyHttpResponse:(NSData *)response
{
    SomeResult *result = [self.parser parseVerifyHttpResponseAndReturnResult:response];
    if (result.token != [NSNull null]) { [self.delegate callBackWithToken:result.token]; }
    if (result.error != [NSNull null]) { [self.delegate callBackWithError:result.error]; }
}

So 2 part question

  1. why can’t I write a test to prove this? Any time I set the error or token to NULL or NSNull it works fine (yet this code was required for production to work)

  2. why would the production code only fail the conditional if I put the != [NSNull null] (yet I can’t seem to get anything but <null> when I NSLog the values while I run it in the simulator?

Keep in mind the token/error properties look like this on the SomeResult object

@interface SomeResult : NSObject

@property (strong, nonatomic) NSString *token;
@property (strong, nonatomic) NSString *error;

@end
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T12:12:39+00:00Added an answer on June 6, 2026 at 12:12 pm

    Your original code and tests are expecting either token or error to be nil, not [NSNull null]. Presumably when you run it against a production endpoint, your parser is setting the value to [NSNull null].

    These tests should pass with your modified code:

    - (void)testVerifyCallbackInvokesErrorCallbackOnDelegateWhenParserReturnsError
    {
        SomeResult *result = [[SomeResult alloc] init];
        result.error = @"fail";
        result.token = [NSNull null];
        [[self.delegate expect] callBackWithError:@"fail"];
        [[self.delegate reject] callBackWithToken:OCMArg.any];
        [[[self.parser stub] andReturn:result] parseVerifyHttpResponseAndReturnResult:nil];
        [self.sut callBackWithVerifyHttpResponse:nil];
        [self.delegate verify];
    }
    
    - (void)testVerifyCallbackInvokesTokenCallbackOnDelegateWhenParserReturnsToken
    {
        SomeResult *result = [[SomeResult alloc] init];
        result.token = @"token";
        result.error = [NSNull null];
        [[self.delegate expect] callBackWithToken:@"token"];
        [[self.delegate reject] callBackWithError:OCMArg.any];
        [[[self.parser stub] andReturn:result] parseVerifyHttpResponseAndReturnResult:nil];
        [self.sut callBackWithVerifyHttpResponse:nil];
        [self.delegate verify];
    }
    

    When you’re dealing with a web service and/or a third party parser that could change its behavior subtly, it’s good to code defensively. You could handle both nil and NSNull:

    - (void)callBackWithVerifyHttpResponse:(NSData *)response
    {
        SomeResult *result = [self.parser parseVerifyHttpResponseAndReturnResult:response];
        if (result.token && result.token != [NSNull null]) { [self.delegate callBackWithToken:result.token]; }
        if (result.error && result.error != [NSNull null]) { [self.delegate callBackWithError:result.error]; }
    }
    

    You may also want to make this an if/else–either test for error first, and never set the token if there’s an error, or ignore the error if you get a token. If you don’t want to ever call both callbacks, then make it impossible in your code paths.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

For some reason, after submitting a string like this Jack’s Spindle from a text
I have a string like this: La Torre Eiffel paragonata all&#8217;Everest What PHP function
I'm parsing an RSS feed that has an &#8217; in it. SimpleXML turns this
I have this code: - (void)parser:(NSXMLParser *)parser foundCDATA:(NSData *)CDATABlock { NSString *someString = [[NSString
I'm new to using the Perl treebuilder module for HTML parsing and can't figure
link Im having trouble converting the html entites into html characters, (&# 8217;) i
I have just tried to save a simple *.rtf file with some websites and
I want to count how many characters a certain string has in PHP, but
I would like to count the length of a string with PHP. The string
I've got a string that has curly quotes in it. I'd like to replace

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.