alma::acs::nc::ConsumerWithComponentClientTestCaseTest Class Reference

Inheritance diagram for alma::acs::nc::ConsumerWithComponentClientTestCaseTest:
Inheritance graph
[legend]
Collaboration diagram for alma::acs::nc::ConsumerWithComponentClientTestCaseTest:
Collaboration graph
[legend]

List of all members.

Public Member Functions

 ConsumerWithComponentClientTestCaseTest () throws Exception
void setUp () throws Exception
void tearDown () throws Exception
void testNoOp1 () throws Exception
void testNoOp2 () throws Exception

Private Member Functions

void channelUp () throws AcsJException, InterruptedException
void channelDown () throws AcsJException
boolean namingBindingsContain (String firstBindingName) throws AcsJException

Private Attributes

Helper ncHelper
EventChannel channel

Static Private Attributes

static final String channelName = "dummyTestChannel"

Detailed Description

This test should investigate why the ComponentClientTestCase environment fails to create and destroy a notification channel repeatedly.

This problem first showed up in ACSLaser/laser-source when modular tests were converted from (TestCase using ComponentClient) to ComponentClientTestCase. There the Consumer class could not be reinstantiated after a previous test had disconnected the Consumer.


Constructor & Destructor Documentation

alma::acs::nc::ConsumerWithComponentClientTestCaseTest::ConsumerWithComponentClientTestCaseTest (  )  throws Exception [inline]

Member Function Documentation

void alma::acs::nc::ConsumerWithComponentClientTestCaseTest::channelDown (  )  throws AcsJException [inline, private]
void alma::acs::nc::ConsumerWithComponentClientTestCaseTest::channelUp (  )  throws AcsJException, InterruptedException [inline, private]
boolean alma::acs::nc::ConsumerWithComponentClientTestCaseTest::namingBindingsContain ( String  firstBindingName  )  throws AcsJException [inline, private]
void alma::acs::nc::ConsumerWithComponentClientTestCaseTest::setUp (  )  throws Exception [inline]

Starts CORBA in the client process and connects to the manager and logger.

Subclasses that override this method must call super.setUp(), likely before any other code in that method.

See also:
junit.framework.TestCase::setUp()

Reimplemented from alma::acs::component::client::ComponentClientTestCase.

References channelUp().

void alma::acs::nc::ConsumerWithComponentClientTestCaseTest::tearDown (  )  throws Exception [inline]

Releases all previously obtained components (using manager), logs out from the manager, and terminates the CORBA ORB.

Subclasses that override this method must call super.tearDown(), likely after any other code in that method.

See also:
junit.framework.TestCase::tearDown()

Reimplemented from alma::acs::component::client::ComponentClientTestCase.

References channelDown(), and alma::acs::component::client::ComponentClientTestCase::m_logger.

void alma::acs::nc::ConsumerWithComponentClientTestCaseTest::testNoOp1 (  )  throws Exception [inline]
void alma::acs::nc::ConsumerWithComponentClientTestCaseTest::testNoOp2 (  )  throws Exception [inline]

This method will never be called because the second setUp() call will hang in channelUp

References alma::acs::component::client::ComponentClientTestCase::m_logger.


Member Data Documentation

Referenced by channelDown(), channelUp(), and testNoOp1().

final String alma::acs::nc::ConsumerWithComponentClientTestCaseTest::channelName = "dummyTestChannel" [static, private]

Referenced by channelDown(), and channelUp().


The documentation for this class was generated from the following file:

Generated by  doxygen 1.6.2