On 22 Mar 2013, at 17:07, Gregory Casamento wrote: > I'm thinking that some tests of GUI classes might be in order as well. I've > been thinking lately about how best to test GUI. > > > On Fri, Mar 22, 2013 at 12:49 PM, Richard Frith-Macdonald > <[email protected]> wrote: > > On 22 Mar 2013, at 16:32, Gregory Casamento wrote: > > > I'm wondering if it might not be a good idea to have a test which looks at > > all classes which implement NSCoding and archives and unarchives them to > > check that the result is what is expected. > > The test framework has test_NSCoding() which does this (and > test_keyed_NSCoding() for classes which support keyed coding). > > > Also, it might be a good idea to have a set of data which was archived on a > > 32 bit machine and on a 64 bit machine etc and check to see that machines > > of all architectures and word sizes can read archives by all other > > platforms. > > The tests in the coding subdirectory do at least some of that. IIRC they > test 32bit archives ... adding 64bit archives would be nice.
While the sets of archived data in the coding dsubdirectory of the base testsuite are obviously base-specific, the test_NSCoding() and test_keyed_NSCoding() functions are general purpose, applying to GUI (or in fact any) classes. _______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
