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 98906 - Cannot generate a TestCase using JUnit wizard
Summary: Cannot generate a TestCase using JUnit wizard
Status: RESOLVED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: junit-issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-26 05:28 UTC by deepakjacob
Modified: 2007-04-11 07:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
JUNIT Test Error Message (27.18 KB, application/octet-stream)
2007-03-26 19:18 UTC, deepakjacob
Details

Note You need to log in before you can comment on or make changes to this bug.
Description deepakjacob 2007-03-26 05:28:38 UTC
Cannot generate a testcase with netbeans 6 200703231900 using wizard provided in
the IDE.
Comment 1 Jan Lahoda 2007-03-26 07:33:49 UTC
Could you please describe in detail what are you trying to do and what does not
work? I have tried to create a test case in a recent build of the IDE, and it
worked without a problem for me. Is there any exception? Could you please attach
your messages.log (${userdir}/var/log/messages.log). Thanks.
Comment 2 deepakjacob 2007-03-26 19:18:21 UTC
Created attachment 39968 [details]
JUNIT Test Error Message
Comment 3 deepakjacob 2007-03-26 19:21:02 UTC
Anyway I am not able to regenerate the error today.

Sending thre error log.

please note that i was using nb 5.5. when i opened
nb 6 for the first time it asked me whether i need to import 5.5's setting. i
pressed ok. can it be a mismatch plbm ?
Comment 4 Marian Petras 2007-04-11 07:40:33 UTC
I am sorry, the attached log file contains nothing related to creating JUnit
tests so I have no information about what was wrong. It might be related to
importing settings from 5.5 but it is hard to say since no relevant information
is available.

Due to lack of information and due to the fact that the exception cannot be
reproduced, I close this bug report as INVALID. Feel free to reopen it once you
find more information or if you encounter the issue again.