Hi All, Due to the complex history of many of the classes now packaged inside the toolkit there is a wide variance in the quality of the specification/documentation amongst the classes. Writing useful conformance tests for the toolkit requires having a good definition of two things. Firstly what is/should be public API and what shouldn't, and then for those classes that are public API, what defined behaviors should form the specification for each API type.
I imagine there will be two types of contributors to this discussion, original authors of some of the classes (mostly TC internal people), and those with no prior knowledge of the actual source code implementations. I'm keen to solicit opinions from both sets of people since those with knowledge of current implementations may well have pre-conceived ideas about the current behaviors, in particular around behavior in exceptional situations and corner cases. I'll be sending out a series of emails with my initial thoughts regarding existing packages. I'll be breaking the discussion down in to multiple emails most likely on per-package/area basis. Please respond if you have any thoughts at all... otherwise you will all be stuck with my interpretation of everything... you have been warned. Thanks, Chris _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
