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.
Summary: | No test methods are generated | ||
---|---|---|---|
Product: | java | Reporter: | Jiri Skrivanek <jskrivanek> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | CLOSED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jiri Skrivanek
2004-10-19 10:09:24 UTC
Fixed - I rollbacked the change which caused this bug. The bug was not caused by the last commit to JUnit. It is probably outside the module. a) I tried it before I commited, including commit-validation tests and it worked. b) I just checked-out all other sources, thus, with the changes to templates still in, tried it out and it didn't work. I'm reopening it. I'll investigate the real cause and reassign to the responsible module. The bug is in java-jmi. The problem is that the class doesn't appear to contain the methods (obtained through JavaClass.getFeatures) until after IDE restart. After restart, it works fine - the methods are there. It is not enough to explicitly save the file. It is not enough to close and reopen the project, the ide must be restarted. Maybe issue 50590 is also related. Good point! It looks very much like it. In issue 50590, Hanz says: > Looks like problem is caused by src hierarchy. > The piece of code [snip] > returns SourceElement in place of MethodElement! In JUnit, I filter all features returned by JavaClass.getFeatures and only MethodElement instances are processed further. Fixed. *** This issue has been marked as a duplicate of 50591 *** Verified in build 20041019-2335. |