當程式開發人員修改部分程式碼，可能必須重新執行舊有的系統測試案例(system test cases)，但測試案例的數量往往隨著系統的發展而攀升，程式開發人員必須耗費時間執行大量系統測試案例。系統測試案例執行的代價通常很高，但是要降低這些代價而採用測試自動化往往必須先付出一筆昂貴的代價。 因為單元測試案例(unit test cases)的執行代價相較於系統測試案例自動化低，且較容易進行自動化，所以近年來有一些研究，致力於在系統的執行過程中自動將系統測試案例切割並產生單元測試案例的轉換技術─錄製系統測試案例並重播單元測試案例(capture system test cases and replay unit test cases)。 建構這樣完全自動化的轉換系統其實有一定的困難度。本篇論文將此技術實際應用，探討將此技術實際完全自動化會遇到哪些問題，再逐項分析進行自動化的困難以及可能性。 When the code of system under test is modified, system test cases must be rerun for regression. However, the number of system test cases increases as the system grow. Developers typically run the new version of program against all system test cases to validate that the changes made on the program do not break the system. It can take a lot of time and efforts to rerun all system test cases manually. Test automation in principle can alleviate the problem. However, system-level test automation may require a one-time investment first, which can be costly depending on the types of applications. Contrast to system test cases, unit test cases could be executed more efficiently. Recent researches have begun to study a transformation technique which captures system test cases and replays them as unit test cases. However, building such a transformation system might not be as easy as it may seem. In this thesis, we manually simulate the transformation technique to generate unit test cases and then analyzes cost of this approach and the problems that could be raised in this study.
