View - HEPHY

tsframework::CellOperationTestOperationBaseConfiguredTestOperationPatternTestOperationInterconnectionTestOperationFunctionTestOperationFINORTestOperationFigure 5.6: Test Operation class hierarchy.• A TestResult contains the entire result information from an executed test instance.• A TestSpecificationEditor is a GUI widget that can be used to create, viewor edit TestSpecification objects.• A TestResultBrowser is a GUI widget than displays test results.Each of the three existing tests then provides an implementation for these classes.However, the inheritance hierarchy is not entirely uniform because the functional differencesbetween the pattern test and the FINOR test are rather small. It is thereforenot necessary to have separate TestSpecification and TestResult subclasses,and instead there are common PatternTestSpecification and PatternTestResultclasses for both. In addition, the inheritance hierarchy contains an intermediate layernamed ConfiguredTestOperation (and so on) for tests that require the hardware tobe configured before executing the tests. This is common functionality for all existingtests. Fig. 5.6 shows the inheritance hierarchy for the operation classes, where theentire hierarchy is expressed.5.3.3 Integration with Existing GT/GMT CellsThe GT and GMT cells already implement commands for hardware configurationfrom the central database, normally used to set up the hardware from the RCMS63