Test purposes have been presented as a solution to avoid the state space explosion when selecting test cases from formal models. Although such techniques work very well with regard to the speed of the test derivation, they leave the tester with one important task that influences the quality of the overall testing process: Test purposes have to be formulated manually. In this paper, we present an approach that assists a test engineer with test purpose design in two ways: It allows automatic generation of coverage based test suites and can be used to automatically exercise those aspects of the system that manually test purposes missed. We consider coverage of LOTOS specifications, and show how labeled transition systems derived from such specifications have to be extended in order to allow the application of logical coverage criteria to LOTOS specifications. We then show howexisting tools can be used to efficiently derive test cases and suggest how to use the coverage information to minimize test suites while generating them.