andrewkeller/REALbasic-Common-KFS-BSD — Issue #69: Make test class objects private to an arbiter
Author: andrewkeller
Created: 2011-10-31 02:48:32+00:00
State: open
Labels: new feature, overhaul

Not sure if this is a good idea, so I'm writing it down so I can have a conversation about it.

Is it a good idea to make test class instances completely private and internal to a UnitTestArbiterKFS object?

If implemented, an arbiter would be provided Introspection.TypeInfo objects, rather than UnitTestBaseClassKFS objects. The Introspection.TypeInfo objects can be created using the GetTypeInfo function.

Advantages:

* A test class object would be completely private to an arbiter (all the way from initialization to deallocation), which opens up the door to simplifying the UnitTestBaseClassKFS class. For example, we could drop support for multiple arbiters running tests on the same test class object, which accounts for a significant amount of the existing complexity in the UnitTestBaseClassKFS class.

Disadvantages:

* A test class object would be completely private to an arbiter, and _nothing_ would be able to access it outside of the arbiter.
* Do we care?