This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 41330 - Test coverage
Summary: Test coverage
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks: 27194
  Show dependency tree
 
Reported: 2004-03-25 08:53 UTC by Jaroslav Tulach
Modified: 2006-03-24 10:04 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2004-03-25 08:53:56 UTC 
There is a typo in JPDAThreadGroup's method. That
probably means nobody ever used it. Obvious
suggestion - write a test. 

This is a general request, close it with
description how you approached the tests, what
they test, how we can try them. So we can do real
verification of this issue.
Comment 1 Jaroslav Tulach 2004-03-25 09:06:10 UTC 
Of special interest are tests for debugger core, jpda, lookup and
interoperability with rest of NetBeans (issue 41332).
Comment 2 Maros Sandor 2004-06-17 15:29:49 UTC 
Unit tests are available in debuggercore and debuggerjdpa module 
(main modules, test/unit directories) and they test debugger core and 
jpda respectively. Tests in core work with a fake debugger engine 
provider and test breakpoints and watches registration and debugger 
startup. JPDA tests launch a debugee VM with a sample class and tests 
various aspects of JPDA API: connectors, all sorts of breakpoints, 
stack information, locals info, expression evaluation and stepping. 
Lookup tests are part of the debugger core test suite.
Comment 3 Jaroslav Tulach 2004-06-22 15:56:33 UTC 
The tests are there and the coverage increase is amazing.