Skip to content

Commit c26e7d9

Browse files
authoredJan 24, 2020
Update INSTALL.md
1 parent 8daff1b commit c26e7d9

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed
 

‎INSTALL.md

+10-4
Original file line numberDiff line numberDiff line change
@@ -22,23 +22,29 @@ Once the virtual machine is imported, it will appear in your VirtualBox Manager
2222

2323
<img src="https://drive.google.com/uc?id=1VjrcBPwrz4LO8cwlspb0TmEUcqwMoCp-" alt="VirtualBox Manager"/>
2424

25-
Once the virtual machine loads, Eclipse will open -- this process may take a few minutes. Once Eclipse opens, there will be 7 files opens labeled *Defect 0- Defect 6*. 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 associated with *Defect_0_Training*.
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*.
2626

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.
2728

2829
## Running Holmes
2930

3031
To see Holmes output for each defect:
3132

3233
1. Double-click a TODO in the Tasks View to get to the failing test.
33-
* *Defect 0* 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).
3434

35-
* *Defects 1-6* show the pre-processed output that participants saw during the user study.
35+
<img src="https://drive.google.com/uc?id=1fpS9WQLitBs_fk07tuBtkhkkrLHGAh0x" alt="Eclipse TODOs"/>
3636

37-
2. Highlight the method that takes the input being tested. Each TODO is followed by comments that specify what we asked participants to do and the method to highlight.
37+
2. Highlight the method that takes the input being tested, as shown below. Each TODO is followed by comments that specify what we asked participants to do and the method to highlight.
38+
39+
<img src="https://drive.google.com/uc?id=1Bs8DV4B1rsqqr8PDWPZbiQL45HFkcqjv" alt="Highlighting target method"/>
3840

3941
3. Right-click the highlighted method and click **"Run Holmes"** in the pop-up menu.
4042

4143

44+
*Defect 0* 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).
45+
46+
*Defects 1-6* show the pre-processed output that participants saw during the user study.
47+
4248
If you are running Holmes on *Defect 0*, 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.
4349

4450
If you are running Holmes on *Defects 1-6*, 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.

0 commit comments

Comments
 (0)
Please sign in to comment.