On 22 Mar 2013, at 19:58, Gregory Casamento wrote:
Richard,
I think putting tests in GUI for archiving is important since the point is not
so much to test the archiver itself but that the GUI classes are, indeed,
archiving themselves in a way which is universal for all platforms.
Sure ... my point was simply that we already have them built in to the test
framework itsself ... so the GUI testsuite should use the functionality we
already have.
The current coding testing functions test whether the decoded object is the
same as the original object by calling -isEqual:
For classes where the standard equlity test isn't enough we can implement
-isEqualAfterCoding: in a category on the class.
Of course, no standardised test code can possibly cope with all situations, but
I'd recommend you start by calling test_NSCoding() and test_keyed_NSCoding()
for all the GUI classes, then think about how things might be extended to
handle any special cases.