Skip to content

Commit ef8854d

Browse files
authoredJan 26, 2020
Update INSTALL.md
1 parent 1585351 commit ef8854d

File tree

1 file changed

+0
-30
lines changed

1 file changed

+0
-30
lines changed
 

‎artifact_documentation/INSTALL.md

-30
Original file line numberDiff line numberDiff line change
@@ -21,33 +21,3 @@ To load the virtual machine, you will need to import the **CausalTesting_Artifac
2121
Once the virtual machine is imported, it will appear in your VirtualBox Manager as **CausalTesting_Artifact**. You can now start the virtual machine by clicking the green **"Start"** arrow at the top of the VirtualBox Manager (see screenshot below).
2222

2323
<img src="https://drive.google.com/uc?id=1VjrcBPwrz4LO8cwlspb0TmEUcqwMoCp-" alt="VirtualBox Manager"/>
24-
25-
Once the virtual machine loads, Eclipse will open -- this process may take a few minutes. Once Eclipse opens, there will be 7 projects in the Project Explorer labeled *Defect 0- Defect 6*.
26-
27-
At the bottom of the window, the Tasks View is open with a list of TODOs. Each TODO is attached to the failing test for each defect. For example, **TODO: Test 00 (Training)** is attached to the failing test *test_toBoolean_String()* which exposes *Defect 0* in the *toBoolean()* method.
28-
29-
## Running Holmes
30-
31-
To see Holmes output for each defect:
32-
33-
**1. Double-click a TODO in the Tasks View to get to the failing test that exposes the defect.**
34-
Each TODO is followed by comments that specify what we asked participants to do and the method to highlight for executing Holmes.
35-
36-
<img src="https://drive.google.com/uc?id=1fpS9WQLitBs_fk07tuBtkhkkrLHGAh0x" alt="Eclipse TODOs"/>
37-
38-
2. Highlight the method that takes the input being tested, as shown below.
39-
40-
<img src="https://drive.google.com/uc?id=1Bs8DV4B1rsqqr8PDWPZbiQL45HFkcqjv" alt="Highlighting target method"/>
41-
42-
3. Right-click the highlighted method and click **"Run Holmes"** in the pop-up menu.
43-
44-
<img src="https://drive.google.com/uc?id=1T5IOWdJvIkt6nte0zcKnrlbdPxQzraol" alt="Run Holmes command"/>
45-
46-
47-
**Test 00** runs the test generation portion of Holmes (which does not include execution traces, as this was not automated in the user study version of Holmes). If you are running Holmes on **Test 00**, the editor will automatically go to the top of the file as Holmes generates and executes tests. This process will take a minute or two; eventually the Holmes View will open with results of the execution.
48-
49-
<img src="https://drive.google.com/uc?id=1ZP2c1zftIuyvyyuEPOBj1pTb9mujvi8N" alt="Test 00 Output"/>
50-
51-
**Test 01 - Test 06** show the pre-processed output that participants saw during the user study. If you are running Holmes on **Test 01 - Test 06**, after a few seconds, the Holmes View will open with the pre-processed results used in our user study. For each of these defects, the output includes the original failing test, generated passing tests, and generated faiing tests. You can access the execution trace for each test by clicking the **"See Execution Trace"** button under the test of interest.
52-
53-
<img src="https://drive.google.com/uc?id=1U5LBRjhgRx7kCZpQRWb3qjVoMgNiLzC_" alt="Run Holmes command"/>

0 commit comments

Comments
 (0)
Please sign in to comment.