1 Introduction

1.1 Scope

The changes/improvements in the EiffelStudio Debugger from Eiffel 5.7 to 6.0 are the following.

• 1.1.1 Improved performance and overall robustness, particular for .Net targets.
• 1.1.2 Addition of a console-based debugger via –debug or –loop options.
• 1.1.3 Enhanced Breakpoint Mechanism
  • 1.1.3.1 Tracepoints
  • 1.1.3.2 Hit Counts
  • 1.1.3.3 Conditionals (‘Is True” / “Has Changed”)
• 1.1.4 Improvements in Expression Evaluation
  • 1.1.4.1 Instruction Evaluation (dynamic procedure execution)
  • 1.1.4.2 Expressions are evaluated with no assertions by default but this can altered on an individual expression basis
  • 1.1.4.3 Full support for disabling/restoring assertion checking at runtime for all debuggee targets.
• 1.1.5 Improvements in Debugger Graphical Display
  • 1.1.5.1 Complete Redesign of the Debugging Options Dialog
    • 1.1.5.1.1 Better Dialog for Argument Setting and Working Directory
    • 1.1.5.1.2 Environment variables can now be added or modified for use by the debuggee
    • 1.1.5.1.3 Now Workbench and Finalized versions can be executed outside of the IDE
  • 1.1.5.2 Debuggee can be restarted without un-raising and then re-raising the interface
  • 1.1.5.3 Environment can now be forced to stay in debugger mode
  • 1.1.5.4 New Object Viewer Tool
    • 1.1.5.4.1 Objects can be fully browsed
    • 1.1.5.4.2 Structure can be outputted/dumped to text or XML for a structured of human-readable object representation
    • 1.1.5.4.3 Order of ‘Current Object’, ‘Locals’ and ‘Arguments’ can now be reordered
  • 1.1.5.5 Call Stack Tool now indicates features with a rescue clause
  • 1.1.5.6 Objects Grid has been improved via removal of redundant attributes title row
  • 1.1.5.7 Debugger now shows state of ‘Once Functions’ and now ‘Once Procedures’
  • 1.1.5.8 Improvements to Watch Tool
    • 1.1.5.8.1 Generation of Auto Expressions
    • 1.1.5.8.2 Ability to Save Expressions?
    • 1.1.5.8.3 Allow Object Creation Expressions? (Works for non-generic classes, but not for TUPLE)

1.2 Assumptions

• 1.2.1 All additions and improvements mentioned in 1.1 have been implemented with no known bugs

2 System Test Plan for the EiffelStudio Debugging Mechanism (Debugger)

2.1 Objectives

A Test Plan for the EiffelStudio Debugging Mechanism should support the following objectives:

• 2.1.1 To document the methods used and results attained when testing the additions/improvements to the debugging facilities .
• 2.1.2 To communicate to the Debugger Team the any issues found due to the resulting test failures/discrepancies.
• 2.1.3 To define the sources of the information used to prepare the plan.
• 2.1.4 To define the test tools and environment needed to conduct the system test.

2.2 Background

From November 2006 to May 2007, the EiffelStudio Debugging Mechanism Team have developed improvements and new features for new Eiffel Studio version 6.0.

2.3 Scope

This test plan covers a full test of the EiffelStudio Debugging Mechanism’s new features and improvements which were developed between EiffelStudio versions 5.7 and 6.0.

2.4 References

Online Google doc: http://docs.google.com/Doc?id=dgvcsvkd_184ffqdn DEBUGGER/Jocelyn part.

3 Test items

• 3.1 EiffelStudio Source Code and supporting library code
• 3.2 EiffelStudio executable