PROJECT: BOGOR JAVA ENVIRONMENT FOR ECLIPSE DELIVERABLE: TEST PLAN

Transcription

1 PROJECT: BOGOR JAVA ENVIRONMENT FOR ECLIPSE DELIVERABLE: TEST PLAN Date: December 9, 2005 Prepared by: Yong Peng Major Professor: Robby Kansas State University 1

2 Table of Content 1. TEST PLAN IDENTIFIER INTRODUCTION REFERENCE TEST ITEMS FEATURE TO BE TESTED FEATURE NOT TO BE TESTED APPROACH ITEM PASS/FAIL CRITERIA SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS SUSPENSION RESUMPTION REQUIREMENT TEST DELIVERABLES TEST LOG TEST TASKS TEST CASE1 SR1.1, SR Test Case1.1 SR Test Case1.2 SR TEST CASE2 SR2.1, SR2.2, SR2.3, SR Test Case2.1 SR2.1, SR2.2, SR Test Case2.2 SR TEST CASE3 SR TEST CASE4 SR4.1, SR4.2, SR

3 1. Test Plan Identifier Bogor-Java Environment for Eclipse. 2. Introduction This document describes the methods that will be used to test the Bogor-Java Environment for Eclipse. Bogor-Java Environment for Eclipse allows Java developers to incrementally compile Java into BIR, to view the compiled BIR in Bogor VM viewer, to use the newly created launcher to invoke Bogor to model check Java system, and to trace errors in Java code. Each plug-in will be treated as a separate module of the system. Each module will be tested with respect to the requirements as described in the vision document. 3. Reference Vision Document: 4. Test Items The following core system modules will be tested. Incremental compilation. Bogor VM viewer. Launcher. Error trace. 5. Feature to be tested The following list of features will be tested. These features can be referenced in the Vision document. SR1.1 (Critical requirement) - Incremental Compilation SR1.2 (Critical requirement) Add a new nature into Java project SR2.1 (Critical requirement) Create a launcher SR2.2 (Critical requirement) Create a main tab SR2.3 (Critical requirement) Create a properties configuration tab SR2.4 Output model check result into Eclipse console SR3 (Critical requirement) Trace errors in Java program SR4.1 (Critical requirement) Create a view to display compiled BIR SR4.2 - Highlight Java in java editor SR4.3 - Highlight BIR in Bogor VM Viewer 3

4 6. Feature not to be tested The content of generated BIR and the result of model checking will not be tested. 7. Approach Only functional black box testing will be performed to test the functionality of Bogor-Java Environment for Eclipse. User actions will be simulated through a set of test scenarios. Each scenario will trace back to a requirement listed in the Vision document. A GUI recorder and playback tool, TPTP Automated GUI Test Tool, will be used to perform regression tests. This tool is developed under the TPTP test framework. Users can use this tool to record GUI actions in Eclipse and play them back to verify the functionality of their product. 8. Item Pass/Fail Criteria Test cases executed on Bogor-Java Environment for Eclipse will pass if they meet the requirements as mentioned in the Vision document. A test case will fail if any behavioral expectation is not met as described. 9. Suspension Criteria and Resumption Requirements 9.1. Suspension If a test case fails, testing will be suspended for all dependent features. The failed test case will be logged into a Testing Resulting along with a description of the failure Resumption Requirement Testing for the failed test case will resume after the bug has been identified and resolved. Independent test cases will continue to be executed in parallel to bug fixing. 10. Test Deliverables Testing Results The Testing Results documents all test cases and records the pass or failure status of test cases. A test case that fails will have the reasons for failure and suggested solutions documented. 4

5 11. Test Test Case1 SR1.1, SR1.2 The purpose of this test is to test incremental plug-in. This test includes two sub-tests Test Case1.1 SR1.2 This test case will execute Figure in formal specification document. The number in the tasks section is the same number in FSM. 1. Create Java project 2. Delete Java project 3. Check BB nature from menu 4. Uncheck BB nature from menu 5. Delete Java project If task#1 executes, a new Java project should be created and then open project properties panel, there should have only one builder Java builder. If 1 3 executes, open project properties panel, there should have two builders: Java and Bytecode to BIR Builder If executes, open project properties, the Bytecode to BIR Builder should disappear. If 1 2, 1 3 5, or executes, Java project should be deleted Test Case1.2 SR1.1 This test case will execute Figure in formal specification document. The number in the tasks section is the same number in FSM. 1. Delete Java (BIR deleted) or delete BIR 2. Open/New Java 3. Delete Java (BIR deleted) or Close editor 4. Delete BIR 5. Edit 7. Delete Java (BIR deleted) or Close editor without save 8. Undo 9. Edit/Undo/ delete BIR 5

6 10. Save/Close editor & save If task#1[delete Java] executes, the Java file should be deleted and the BIR should be deleted if any If task#1[delete BIR] executes, the BIR file should be deleted If 2 3[delete Java] executes, Java file and BIR should be deleted and the editor should be closed. If 2 3[close] executes, the editor should be closed. If 2[new Java] executes, the eclipse event should be triggered to create the new class and BIR, and then the system state should be forwarded back to Java editor (clean). The path in FSM is 2[new Java] If 2[open] 5 10[save] executes, the class and BIR should be updated, and then the system state should be forwarded (action [12]) back to Java editor (clean). The path in FSM is 2[open] 5 10[save] 12. If 2[open] 5 10[close editor and save] executes, the system state should be forwarded (action [11]) back to Java editor closed. The path in FSM is 2[open] 5 10[close editor and save] 11. If 2 5 7[delete Java] executes, Java file should be deleted and BIR should be deleted if any, and the Java editor should be closed. If 2 5 7[close editor without save] executes, Java editor should be closed. If 2 4 executes, BIR should be deleted if any. If 2 5 8[undo] executes, the state should be back to Java editor clean after undo all previous actions. If executes, the state should be in Java editor dirty Test Case2 SR2.1, SR2.2, SR2.3, SR2.4 The purpose of this test case is to test system requirements for launcher plug-in. Test case 2.1 and 2.2 will execute Figure 1.3 in formal specification document Test Case2.1 SR2.1, SR2.2, SR Click Run Edit 4. Load default Edit Config 6

7 7. Load default Click Config Tab Run Close Run/Apply Click Main Tab 20. Close/Run If Run is clicked If 10, 12, 15, 17, 19, or 20[close] executes, the state should go to Launch Pad closed. If 20[run] executes, eclipse action should be triggered to invoke Bogor. If 11[apply], 16[apply], or 18[apply] executes, the state should go to config copied to work copy. If 11[run], 16[run], or 18[run] executes, the state should go to config copied to work copy. The path in FSM is 11/16/ If 1 executes, eclipse action should be triggered to open main tab after launch pad is opened. The path in FSM is 1 2. If or executes, the values in main tab should be changed if any changes are made. If 1 2 8, , , , , , , , , or executes, the main tab and config tab should be switched accordingly. If , , or executes, the values in config tab should be changed if any changes are made. If , or executes, the default configuration should be loaded into the tab Test Case2.2 SR2.4 Since system requirement 2.4 is trivial, it can be tested by checking if result displays in eclipse console after run has been clicked. 7

8 11.3. Test Case3 SR3 The purpose of this test case is to test system requirements for Java error trace plugin. This test case will execute Figure 1.4 in formal specification document. 1. Click Bogor Trail File Step through the errors Close combo view/trail editor If 4, or 5 executes, it should go back to the start state. If or 1 2 executes, the corresponding Java code should be highlighted if there is a line number in trail. The path in FSM is or If 1 executes, it should open Java editor, Counter Examples Combo View, and Bogor trail editor Test Case4 SR4.1, SR4.2, SR4.3 The purpose of this test case is to test system requirements for Bogor VM view plugin. This test case will execute Figure 1.2 in formal specification document. One assumption to execute this test case is that the Java editor has been opened. 1. Open Close Click code in Java editor Click BIR in View If 2, 4, or 6 executes, the view should be closed. If 1 executes, BIR should be displayed in the view if BIR exists. If executes, Java code should be highlighted. The path in FSM is If or executes, BIR should be highlighted. If or executes, Java code should be highlighted. The path in FSM is or