Difference between revisions of "EDT:Debug Regression Testing"

From Eclipsepedia

Jump to: navigation, search
(New page: The following test scenarios should be run each release. 0. Common scenarios to be run as part of each of the other scenarios Stepping *Step into *Step over *Step return Run to ...)
 
Line 1: Line 1:
The following test scenarios should be run each release.
+
The following test scenarios should be run each release.  
  
 +
<br>
  
 +
'''Common scenarios to be run as part of each of the other scenarios'''
  
0. Common scenarios to be run as part of each of the other scenarios
+
Stepping
  
Stepping
+
*Step into  
 
+
*Step over  
*Step into
+
*Step over
+
 
*Step return
 
*Step return
  
Run to line:
+
Run to line:  
  
*"Ctrl + r" with the cursor on the target line
+
*"Ctrl + r" with the cursor on the target line  
 
*Right-click in the editor and select "Run to Line" with the cursor on the target line
 
*Right-click in the editor and select "Run to Line" with the cursor on the target line
  
Breakpoints
+
Breakpoints  
  
*Can be set by double-clicking the editor's left margin, or right-click the margin to add
+
*Can be set by double-clicking the editor's left margin, or right-click the margin to add  
 
*Can enable/disable breakpoints, changes take immediate effect
 
*Can enable/disable breakpoints, changes take immediate effect
  
Variables view
+
Variables view  
  
*All variables in scope are listed
+
*All variables in scope are listed  
*Value and type for each variable looks correct
+
*Value and type for each variable looks correct  
 
*Values can NOT be changed during debugging (future feature)
 
*Values can NOT be changed during debugging (future feature)
  
Debug view
+
Debug view  
  
*When suspended, the function stack looks correct
+
*When suspended, the function stack looks correct  
*Stack frames have correct names and line numbers
+
*Stack frames have correct names and line numbers  
 
*Clicking on frames updates the variables view to show that frame's variables, and selects the appropraite line in the editor
 
*Clicking on frames updates the variables view to show that frame's variables, and selects the appropraite line in the editor
  
 +
<br>
  
 +
<br>
  
 +
'''Batch programs (Java)'''
  
 +
TBD<br>
  
1. Batch Java
+
<br>
 
+
 
+
 
+
 
+
 
+
2. Rich UI (JavaScript)
+
  
 +
'''Rich UI Handlers (JavaScript)'''
  
 +
TBD<br>
  
 +
<br>
  
 +
'''Services (Java)'''&nbsp;
  
3. Services
+
TBD

Revision as of 15:27, 5 March 2012

The following test scenarios should be run each release.


Common scenarios to be run as part of each of the other scenarios

Stepping

  • Step into
  • Step over
  • Step return

Run to line:

  • "Ctrl + r" with the cursor on the target line
  • Right-click in the editor and select "Run to Line" with the cursor on the target line

Breakpoints

  • Can be set by double-clicking the editor's left margin, or right-click the margin to add
  • Can enable/disable breakpoints, changes take immediate effect

Variables view

  • All variables in scope are listed
  • Value and type for each variable looks correct
  • Values can NOT be changed during debugging (future feature)

Debug view

  • When suspended, the function stack looks correct
  • Stack frames have correct names and line numbers
  • Clicking on frames updates the variables view to show that frame's variables, and selects the appropraite line in the editor



Batch programs (Java)

TBD


Rich UI Handlers (JavaScript)

TBD


Services (Java) 

TBD