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.
GUI classes not saving themselves correctly was the issue which prompted doing another release since there were bugs in some GUI classes where a type of the wrong size was being encoded. Having these tests would help to eliminate the possibility of this happening.
...Slightly off topic...
This discussion also makes me think about what other tests we can do in GUI to prevent regressions.
I've been wondering if it might not be possible to build a testing framework based on NSEvent so that GUI tests could be scripted instead of manually performed, but that's just a thought at the moment.
GC