A Novel Approach to Develop Composite Component in Extreme Programming with Sequence Test

元件開發是軟體工程中相當重要的一環，隨著時代的演進，元件開發的技術日益提升，元件測試的相關研究也越來越多。在以往的測試策略中，Stub的實作困難以及不必要的測試案例設計，都是造成整個軟體開發延遲的或是花費上升的主要因素。而造成這些因素的不只來自於人的問題，還有測試架構的選擇。因此，對於不同特性的軟體開發相對應的測試架構是相當重要的。 軟體測試在軟體開發中扮演相當重要的角色，其代價相當昂貴，幾乎占了整個軟體開發的一半花費。其中單元測試和整合測試是最基礎的部分，測試元件也是基礎的一部分。在Extreme Programming問世之後，這些組合成軟體的元件也應當有另外的專屬測試架構，特別是上層與下層的元件具有不一樣的特性，應當設計相對應的測試架構。 這篇論文便是提供了測試組合元件的一個架構，這個測試架構不只是解決了過去舊有的測試架構的缺失，更是提供了在回歸測試以及偵錯上更完整的功能。在論文的最後，一個案例研究將會驗證這個測試架構確實是可行及有效率。Component development is the important part of software development. As time goes on, the technique of component development progresses day by day and there are more and more researches related to component test. To develop component with old test theory, the hard stub implementation and unnecessary test case design leads to the extra cost and the delay of the whole software development. These factors may come from the wrong test framework selection. Therefore, it is important to develop the test framework corresponding different feature software. Software testing plays an important role in software development. It is quite expensive process, typically consuming at least 50 percent of the total costs. Unit and integration testing is the fundamental part of software testing and component is a kind of unit testing. After Extreme Programming was born, there should be another test for developing component. Especially, corresponding test framework should be designed for the component with different purpose. A new test framework is provided for testing composite component in this paper. This test framework not only solves many problems about old testing to component but also supports the solution about regression testing and debugging. In the end of paper, a case study is demonstrated to prove that this approach is feasible, effective, and efficient.中文摘要 I Abstract II Chapter 1. Introduction 1 1.1 Motivation 1 1.1.1 Difficult Stub Implementation 1 1.1.2 Unnecessary Test Case in Bottom-up Approach 3 1.1.3 Improper Test to Develop Composite Component in XP 6 1.2 Goal 6 1.3 Organization 7 Chapter 2. Background 8 2.1 Software Testing 8 2.1.1 Unit and Integration Test 10 2.1.2 Regression Test 12 2.1.3 State Test 12 2.2 Debug 13 2.3 Extreme Programming 13 2.4 Component-based Software Engineering 14 Chapter 3. System Overview 16 3.1 Our Environment 16 3.2 Our Architecture 16 3.2.1 The Ant Process 18 3.2.2 The Derived Program 21 3.2.3 The Exchange Process 22 3.2.4 Save the Behavior of Debugging 24 3.2.5 Regression Test and Target Tested Class Selection 25 Chapter 4. Our Implementation 26 4.1 The Modification of Ant 26 4.2 The Generation of Derived Program 27 4.3 The Exchange Process Implementation 28 4.4 The Generation of Test Case Source Code 29 4.5 Debug and Stub Mode 29 Chapter 5. A Case Study 31 5.1 Study Setup 31 5.2 Test Flow 33 5.2.1 The Conceptual Scenario 33 5.2.2 How to Write the Test Case 34 5.2.3 Execute Which Test Case 36 5.2.4 Report and File Change 37 5.2.5 Test Case Specification 38 5.2.6 User Interface 39 5.3 Discussion 40 Chapter 6. Conclusions and Future Works 43 6.1 Conclusions 43 6.2 Future Works 44 References 4