Polyethism and comparability of termite choice assays in a model system using Microcerotermes turneri (Termitidae : Termitinae): Implications for standardised testing techniques

Traditional measures of termite food preference assess consequences of foraging behavior such as wood consumption, aggregation and/or termite survivorship. Although studies have been done to investigate the specifics of foraging behavior this is not generally integrated into choice assay experiments. Here choice assays were conducted with small isolated (orphaned) groups of workers and compared with choice assays involving foragers from whole nests (non-orphaned) in the laboratory. Aggregation to two different wood types was used as a measure of preference. Specific worker caste and instars participating in initial exploration were compared between assay methods, with samples of termites taken from nest carton material and sites where termites were feeding. Aggregation results differ between choice assay techniques. Castes and instars responsible for initial exploration, as determined in whole nest trials, were not commonly found exploring in isolated group trials, nor were they numerous in termites taken from active feeding sites. Consequently the use of small groups of M. turneri worker termites extracted from active feeding sites may not be appropriate for use in choice assays.

A case study in specification and implementation testing

Achieving consistency between a specification and its implementation is an important part of software development In previous work, we have presented a method and tool support for testing a formal specification using animation and then verifying an implementation of that specification. The method is based on a testgraph, which provides a partial model of the application under test. The testgraph is used in combination with an animator to generate test sequences for testing the formal specification. The same testgraph is used during testing to execute those same sequences on the implementation and to ensure that the implementation conforms to the specification. So far, the method and its tool support have been applied to software components that can be accessed through an application programmer interface (API). In this paper, we use an industrially-based case study to discuss the problems associated with applying the method to a software system with a graphical user interface (GUI). In particular, the lack of a standardised interface, as well as controllability and observability problems, make it difficult to automate the testing of the implementation. The method can still be applied, but the amount of testing that can be carried on the implementation is limited by the manual effort involved.