The Application Of Test Management Technology In NC Software Product Line

Recently, the software industry in china has developed rapidly; many advanced technologies including software product line had entered into the domestic enterprises. At present, many enterprises have brought software product line technologies to their respective different domains successfully and have achieved very good results. But it also gives us some problems, one of which is how to process the testing in the product line. As there were still not a widely accepted testing method in product line, organizations that use product line test their system with their own understandings. What is more is to test the product line as single product. Therefore, to organizations that use product line, how to test the product line is a big problem.This paper describes the testing management system in product line, which we developed when we brought product line technology into our numeric control system in our group.We have got some products in the numeric control product line development,including a core asset base, a platform for product integration. In the paper, we analysis the difference between the testing process in the core asset and the product. Combined the system we already have, we give a testing process in the product, which can cooperate with the historic system well.This paper presents a test mission-driven product line testing methods, whether it is integrated product testing or testing of the core assets. They share one testing process, but in some operational target, they are different. We define three states for one testing task; untested task, tested task and history task. The conversion among these states is also the process of the testing. In order to make the conversion among the three states more smooth, we give a uniform xml-based description for the out put of each state. Untested task is the task that has not been tested, when the untested task has been tested, it converts to the state tested state and output a test report, in which the tester describes the testing process in details. The test administrators comprehensive review the test task and the test report to describe how to deal with the test task. whether the administrator how to handle ,the task run into the third state, historic state, and output a handle document, in which the administrator describe how to handle the task in details. This means the end of the test task. The output of the whole process, including task description document, test report and test handle document all will be putted into the base for the future reference. In order to facilitate the interaction, transmission and archiving, we give formal definition of the description for each of the three documents.The test in the product line is the test mission-driven; a test mission can be a test for integration product, and how to make a good mapping relationship between an integration product and the test case in the core asset lib is a problem need to be resolved. We define an architecture testing table, in which we list the test case that must be tested in the product family clearly. In this way, we build a bridge between the product and test case.Finally, this paper described the testing management system we have developed in our product line research group.We use com-based technology to develop the system; it can combine with the other two parts of our product line, development of core asset and the product. Also this paper has proved that the concepts we describe in the paper is feasible.