TS 72 CNDdebugger

Revision as of 13:52, 29 March 2012 by Apepin (Talk | contribs)

C/C++ Pack Test Specification for Debugger

Author: Alexander Pepin
Version: 0.1
Lastupdate: 28.03.2012
Introduction: Test specification for Debugger support in NetBeans 7.2 C/C++ Pack

Contents


Test suite: Debugger Actions

  1. Start debugging
    1. create a sample application
    2. set a breakpoint in the main function
    3. start debugger
      • start via toolbar button
      • start via main menu
      • start via project context menu
    4. verify that debugger started correctly
  1. Step Into Project
    1. create a sample application
    2. do step into project
      1. step into via project context menu
      2. step into via main menu
    3. verify that debugger started correctly
  1. Step Over
    1. create a sample application
    2. do step into project
    3. do step over
      • step over via main menu
      • step over via toolbar
      • step over via shortcut
    4. verify that debugger stepped over correctly
  1. Step Into
    1. create a sample application with functions (e.g. Quote)
    2. do step into project
    3. do step into function
      • step into via main menu
      • step into via toolbar
      • step into via shortcut
    4. verify that debugger stepped into function correctly
    5. do step into system function
      • step into via main menu
      • step into via toolbar
      • step into via shortcut
    6. verify that debugger stepped into function correctly
  1. Step Out
    1. create a sample application with functions (e.g. Quote)
    2. do step into project
    3. do step into function
    4. do step out function
      • step out via main menu
      • step out via toolbar
      • step out via shortcut
    5. verify that debugger stepped out function correctly
    6. do step into system function
    7. do step out system function
      • step out via main menu
      • step out via toolbar
      • step out via shortcut
    8. verify that debugger stepped out function correctly
    9. do step out 'main' function
      • step out via main menu
      • step out via toolbar
      • step out via shortcut
    10. verify that debugger stepped out main function correctly
  1. Continue
    1. create a sample application
    2. set a breakpoint in the main function
    3. start debugger
    4. when debugger stops at BP do continue
      • continue out via main menu
      • continue out via toolbar
      • continue out via shortcut
    5. verify that debugger continued execution correctly
  1. Pause
       create an application with an endless loop
       start debugger
       when debugger starts do pause
           pause out via main menu
           pause out via toolbar
           pause out via shortcut 
       verify that debugger paused execution correctly 
  1. Finish
       create a sample application
       do step into project
       do finish
           finish out via main menu
           finish out via toolbar
           finish out via shortcut 
       verify that debugger finished execution correctly 
  1. Make Current
       create a sample application with functions (e.g. Quote)
       do step into project
       do step into function
       open Call Stack view
       select any stackframe and make it current
       verify that Local Variables view and Watches were updated accordingly 
  1. Pop To Here
       create a sample application with functions (e.g. Quote)
       do step into project
       do step into function
       open Call Stack view
       select caller stackframe and do pop to here
       verify that debugger stops in caller function 
  1. Pop Topmost Call
       create a sample application with functions (e.g. Quote)
       do step into project
       do step into function
       open Call Stack view
       open Debug menu Stack section and do pop topmost call
       verify that debugger stops in topmost caller function 
  1. Make Caller Current
       create a sample application with functions (e.g. Quote)
       do step into project
       do step into function
       open Call Stack view
       open Debug menu Stack section and make caller current
       verify that Local Variables view and Watches were updated accordingly 
  1. Make Callee Current
       create a sample application with functions (e.g. Quote)
       do step into project
       do step into function
       open Call Stack view
       open Debug menu Stack section and make caller current
       open Debug menu Stack section and make callee current
       verify that Local Variables view and Watches were updated accordingly 

Test suite: Debugger Views

  1. check views, open, close etc.
       create a sample application
       do step into project
       check Local Variables view, open, close, change visible columns etc.
       check Watches view, open, close, change visible columns etc.
       check Call Stack view, open, close, change visible columns etc.
       check Sessions view, open, close, change visible columns etc.
       check Breakpoints view, open, close, change visible columns etc.
       check Threads view, open, close, change visible columns etc.
       check Registers view, open, close, change visible columns etc.
       check Memory view, open, close, change visible columns etc. 
  1. Local Variables
       create a sample or some specific application
       do step into project
       check LV on sample projects
       check LV in function
       check numbers (short, int, long, float, double)
       check char
       check pointers
       check arrays
       check unions
       check classes
       check structures
       modify values
       check that values are updated accordingly 
  1. Watches
       create a sample or some specific application
       do step into project
       create a new watch
       customize watch
       delete watch
       watch for function
       modify values
       check that values are updated accordingly 
  1. Call Stack
       create a sample application with functions (e.g. Quote)
       do step into project
       call stack representation
       see call stack actions 
  1. Breakpoints
       create a sample or some specific application
       set several breakpoint
       do step into project
       open Breakpoints view
       check breakpoint representation
       check Go To Source option
       diasable BP
       check that debugger ignore disabled BP
       diasable all BPs
       check that debugger ignore disabled BPs
       enable BP
       check that debugger stops at BP
       enable all BPs
       check that debugger stops at BPs
       customize BP (see Breakpoints section)
           line number
           condition
           event counter
           action
           print text 
       check that changed options has effect
       delete BP
       check that debugger does not stop at BP
       delete all BPs
       check that debugger does not stop at any BPs 
  1. Sessions
       create two or more sample or specific applications
       set several breakpoint in these applications
       do step into project or start debugger for each application
       open Sessions view
       check sessions representation in Sessions view
       switch between sessions and check that Local Variables and Watches are changed accordingly 
  1. Threads
       create a multithreaded application
       do step into project and do steps needed to create new threads
       open Threads view
       check threads representation
       switch between threads and check that Local Variables and Watches are changed accordingly 
  1. Memory
       create an application which modifies memory
       do step into project
       open Memory view and check memory content at the specific address
       do some steps and check that memory content is changed accordingly 
  1. Disassembly
       create a sample application
       do step into project
       open Disassembly view and check disassembled source code
       do some steps and check that cursor moves accordingly 
  1. Registers
       create a sample application
       do step into project
       open Registers view and check its content
       do some steps and check that content is changed accordingly 
  1. Debugger Console
       create a sample application
       do step into project
       open Debugger Console
       do some steps and check console output 
  1. Output
       create a sample application that needs input and produces output (e.g. Quote)
       set Run/Console Type property to Output Window
       do step into project
       do some steps and check that needed data can be entered and check output 
  1. Terminal wnidow
       create a sample application that needs input and produces output (e.g. Quote)
       set Run/Console Type property to Default
       do step into project
       check that a new terminal window appears
       do some steps and check that needed data can be entered and check output 

Test suite: Breakpoints

  1. Function BP
       create a sample application containing function calls (e.g. Quote)
       call Debug/New Breakpoint from the main menu
       set a breakpoint type to Function then enter function name and press OK
       start debugger and check that created breakpoint does work
       check that the breakpoint is displayed correctly in Breakpoints view 
  1. Line BP
       create a sample application
       call Debug/New Breakpoint from the main menu
       set a breakpoint type to Line then enter a desirable line number and press OK
       start debugger and check that created breakpoint does work
       check that the breakpoint is displayed correctly in Breakpoints view 
  1. Address BP
       create a sample application
       do step into project
       open Disassembly view and remember an address where a breakpoint can be set
       call Debug/New Breakpoint from the main menu
       set a breakpoint type to Address then enter a desirable address and press OK
       continue debugging and check that created breakpoint does work
       check that the breakpoint is displayed correctly in Breakpoints view 
  1. Toggle BP
       create a sample application
       click on the gutter next to line in the editor where a breakpoint should be set
       check that the breakpoint is created and a breakpoint annotation is added to the source file in the editor
       start debugger and check that created breakpoint does work
       check that the breakpoint is displayed correctly in Breakpoints view 
  1. Variable BP
  1. System Call BP
  1. Exception BP
  1. Customize BP
       customize (change function/line)
       start debugger and check that created breakpoint does work
       check that the breakpoint is displayed correctly in Breakpoints view 
  1. Conditional BP
       check condition
       check count exceeds
       start debugger and check that created breakpoint does work
       check that the breakpoint is displayed correctly in Breakpoints view 
  1. Actions for BP
       check suspend
       check Thread ID
       check Print Text
       start debugger and check that created breakpoint does work
       check that the breakpoint is displayed correctly in Breakpoints view 

Test suite: Attach To Process

  1. Attach to process
       create a managed application
       run the application (in the IDE or from outside)
       call attach to process dialog
       find the process and attach to it
       debug attached process (check breakpoints, views, etc. )
       repeat the same steps for a makefile based application 
  1. Attach to remote process
       create a managed remote application
       run the application in the IDE
       call attach to process dialog
       select an appropriate remote host
       select an appropriate project name
       find the process and attach to it
       debug attached process (check breakpoints, views, etc. )
       repeat the same steps for a makefile based application 
  1. Attach to GDB server
       create a managed application (local or remote)
       run the application (in the IDE or from outside)
       call attach to process dialog
       select "Gdb Server" in the Debugger combobox
       set an appropriate hostname and port
       select an appropriate project name
       debug attached process (check breakpoints, views, etc. )
       repeat the same steps for a makefile based application 
  1. Simple attach to the running process
       create a managed application (local or remote)
       run the application in the IDE
       press "Attach Debugger" button in the "Build,Run" output tab
       debug attached process (check breakpoints, views, etc. )
       repeat the same steps for a makefile based application
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo