Allen Bierbaum wrote:
> Carsten Neumann wrote:
>
>> Hi,
>>
>> I think I got Allen's OSGNodeTest working (one test still fails, but due
>> to a potential bug). I'll just attach it. The OSGInitFixture should go
>> into the UnitTestUtil dir and all tests that require a call to osgInit
>> need to use a fixture that derives from OSGInitFixture.
>>
>>
> I was thinking we could just put the init call in the main test runner.
> That way we can ensure that init has been called before any tests are
> run and we don't have to deal with fixtures every time. In my opinion
> this would make the tests simpler and avoid bugs.
yeah, you're right, of course.
> The only issue I see with that approach (or yours) is what happens when
> we get to a test where we want to test multiple aspects. As I
> understand it, the number of aspects is fixed at init time in OpenSG
> 1.x. Is there any way with OpenSG 2.0 to adjust the number of aspects
> at run time?
Looking at this method, I doubt it very much, as it checks the system
state to make sure osgInit was not already called:
ThreadManager::setNumAspects(UInt32 uiNumAspects)
Since calling sequences like this: osgInit(); osgExit(); osgInit;
osgExit(); do not work either, I'm out of ideas.
The design of UnitTest++ that simply links all tests together is a
problem here...
Please don't postpone a solution to this to the future, right now it
would not hurt if we had to change the unit test framework (not that I
would want to).
Carsten
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
