Sorry, when I first wrote the response I was under the impression that the channel store XML format was already documented. I see that's not true. I'll see if I can get some info.
Just a friendly *bump* to see if there's any new news here. I'd really like to be able to test (and debug) the channel store functionality before I go through the whole content approval process. From what I understand, I can't even publish products for testing without getting approval first...
Hm, I've never used this feature (nor did I even know it existed until now), but looking at the source, it looks like it works this way. In the directory pkg:/csfake, you can have these xml files:
If you call roChannelStore.FakeServer(true), then the response to a channel store request will be the contents of the corresponding xml file. No transaction with the channel store actually takes place.
The blog post isn't really addressing the issue here. What I, and I'm sure many others, want to know is: what are the contents of the XML files in the csfake directory?
In particular, I am using an in-app update, which doesn't match the catalog/order flow outlined in the blog post. What I need to know is what the GetUpdate.xml file should contain, so that I can test the update flow offline.
The sample code linked in that blog post contains example XML files. While it doesn't have a GetUpgrade.xml file, presumably, it's pretty much identical to the GetPurchases.xml and/or GetCatalog.xml, since the SDK documentation indicates that they all return the same metadata. Have you tried using one of those as a starting point?