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 144748 - Unit tests: FileModelTest suite tests result depends on each other
Summary: Unit tests: FileModelTest suite tests result depends on each other
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Model (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-21 17:45 UTC by Vladimir Kvashin
Modified: 2010-05-21 06:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2008-08-21 17:45:13 UTC
This is an internal issue that results in instable test failures.

It concerns two tests in FileModelTest (org.netbeans.modules.cnd.modelimpl.trace.FileModelTest) suite - 
testResolverClassString and testTemplatePointerToMethod.

The results of testResolverClassString() depend on testTemplatePointerToMethod()
(which isn't correct and sometimes cause instable tests failure)

If the testTemplatePointerToMethod() is run before testResolverClassString(),
then testResolverClassString() runs OK.
Otherwise (if testTemplatePointerToMethod() is not run or is run after testResolverClassString()),
testResolverClassString fails.

The reason is that if testTemplatePointerToMethod() is run first,
the wstring type in the declaration 
wstring str 
(resolver_class_string.cc:21) 
is unresolved (and that's what is stored in the golden file).

If testTemplatePointerToMethod() is not run, wstring is resolved,
therefore test result differ from golden and test fails.
Comment 1 Alexander Simon 2010-05-21 06:38:29 UTC
instability of test was resolved during NB6.9 development