I would have to create a separate test file specifically for this default handler given that other tests assume that the lists SDKs are actually available (e.g. some tests might test for the existence of iphonesimulator 5.0 even though that's not one able in the test file that I created).

My parser only makes the following assumptions about the format of the output:
1) Eack SDK version is surrounded by parentheses in the first line of the SDK block (e.g. "(macosx 10.9)")
2) Each SDK is defined in its own block and is separated by an empty line (in other words, once I know what the SDK is, I'll assume that each line below it is a new attribute/value pair and I'll read those until I get to an empty line).
3) Each attribute/value pair is delimited by a colon.

Based on these assumptions, what this does is replicate what's minimally necessary to ensure that GetAvailableSDKsAndAliases (which calls GetAvailableSDKsInfo) has the right behavior and so that the tests that rely on this default handler pass (i.e. each SDK on its own separate line surrounded by parentheses with a line in between each). I could create a file and throw more information in there, but it would be unnecessary since none of the information would be used by this default handler anyway, and we do test a more realistic case with testGetAvailableSDKsInfo. If we start to have some of the other test cases decide to use information from a fake GetAvailableSDKsInfo call then I feel it would make sense to create a separate test file and have this handler point to that, but until we get to that point I don't think it's worth the effort right now.