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.
jars 0627 -there is only assertEquals(long, long) and assertEquals(Object, Object) in j2meunit framework -it cannot generate assertEquals(boolean, boolean)... the generating must be more 'smart'
possible solutions: for boolean : public void assertTrue(boolean condition) for float, double : public void assertTrue(boolean condition), condition = (expectedResult==result)
fixed. when return type is float, double or boolean AssertTrue(expectedResult==result) is used instead. If there are any other primitive types this should be used for please let me know.
verified in 5.5 build 060711 buils (Beta2 candidate)
there are methods assertEquals(boolean, boolean), assertEquals(double, double), assertEquals(float, float) in JMUnit for CLDC1.1 It would be useful to generate these calls for CLDC1.1
it's not so easy... There can be different configurations on different CLDC version. It's probably better to keep it as it is. Or we should generate code with preprocessor blocks. Decreasing priority and going to fill enhancement.
Correct. Basically what would happen is that this would have to be hooked up to configuration management and I would have to create preprocessor code that would switch back an forth. This is an overkill for test generation since this does exactly the same thing as is and works on everything. If there are requests for this feature from the user community, and there are more than just from a handful of users, I might look into doing this in the future.