- Modeling Examples to Test and Understand Software, Markus Gaelli, PhD Thesis, 2006
- JExample: Exploiting Dependencies Between Tests to Improve Defect Localization, Kuhn etal, 2008
(Phexample is also available on SmalltalkHub)
In spite of the first using "example" as a metaphor and the second using "example" in its name, these are references are about composable tests, not examples.�� While a test can serve as an example, a test is a different concept than an "Example".�� So yes, its a great idea to explicitly define dependencies between tests by them returning instances to be used by other tests, but there are plenty of examples that do not follow that pattern, nor should all examples be forced to follow that pattern, nor should they be force to be tagged something other than an <example>.
Language is a funny thing.�� Dictionaries tend to list all "possible" meanings and don't necessarily indicate which are the more common usage.�� The supporters of "exemplar" seems to have a German background, and maybe the German word "exemplar" is an exact match, but it seems the meaning has evolved since English imported it.�� As a native english speaker, to me "exemplar" has an immediate sense of being too exotic for the purpose, and also more a meaning of "the BEST example/instance of..." - which I think overstates the purpose here. ����
I have marked the more common meanings and underlined significant words in the the supplied dictionary meanings...