Package | Description |
---|---|
com.itko.lisa.coordinator | |
com.itko.lisa.test | |
com.itko.lisa.testing |
Modifier and Type | Method and Description |
---|---|
void |
Coordinator.raiseException(TestRunException ex)
Simulators use this method to propogate a serious test execution
error.
|
Modifier and Type | Method and Description |
---|---|
int |
TestCoordinator.addInstancesToSimulator(java.lang.String simName,
int newInstances)
This is how you can change the number of instances currently running
a test before or during execution.
|
void |
TestRegistry.confirmLicenseRoom(int instances)
This method needs to remain in place for backward compatibility
|
java.util.Map<java.lang.String,java.lang.Integer> |
TestRegistry.findSimulatorsForLoad(java.lang.Integer instances,
java.lang.String coordServerName,
com.itko.lisa.test.Configuration config)
This method will work with all known simulators to get the given number
of instances placed on the running Simulators
The default implementation of the TestRegistry does not attempt to
atomically stage tests, it would be too expensive.
|
java.lang.String |
Coordinator.notifyOfRemoteEventListener(java.lang.String listenerId,
int[] filter)
There is a JMS Topic related to this Coordinator that remote event listeners use to get events
pushed into their consumers.
|
void |
TestRegistry.putCoordinatorServer(java.lang.String labName,
com.itko.lisa.net.CoordinatorServerClient fUrl)
This method enables you to construct a new CoordinatorServer
and plug it into this manager so that it is visible throughout the network
and can be health monitored.
|
void |
TestRegistry.putLiveWorkstation(com.itko.lisa.dradis.client.ComponentBeanEx cb) |
void |
TestRegistry.putSimulator(java.lang.String labName,
com.itko.lisa.net.SimulatorServerClient sUrl)
This method enables you to construct a new SimulatorServer
and plug it into this manager so that it is visible throughout the network
and can be health monitored.
|
void |
TestRegistry.putVirtualServiceEnvironment(java.lang.String labName,
com.itko.lisa.net.VSEClient vseUrl)
This method enables you to construct a new VirtualServiceEnvironment
and plug it into this manager so that it is visible throughout the network
and can be health monitored.
|
static int |
TestRunner.runThisTest(Coordinator c,
int updateSecs,
java.io.PrintStream statusOut)
This method simplifies exeuting a test case and receiving stats output through
the given stream.
|
static int |
TestRunner.runThisTest(Coordinator c,
int updateSecs,
java.io.PrintStream statusOut,
TestRunner.ExecutionMode mode)
This method simplifies exeuting a test case and receiving stats output through
the given stream.
|
static int |
TestRunner.runThisTest(java.util.List<?> cList,
Coordinator c,
int updateSecs,
java.io.PrintStream statusOut,
java.lang.String htmlReportPath,
TestRunner.ExecutionMode mode)
This method simplifies exeuting a test case and receiving stats output through
the given stream.
|
static int |
TestRunner.runThisTest(java.util.List<?> cList,
Coordinator c,
int updateSecs,
java.io.PrintStream statusOut,
TestRunner.ExecutionMode mode)
This method simplifies exeuting a test case and receiving stats output through
the given stream.
|
com.itko.lisa.net.SimulatorClient |
SimulatorServer.startSimulator(java.lang.String stgUniqueId)
This is the only truly useful method in this interface for most developers.
|
void |
Coordinator.startTest()
Starts execution of the test.
|
Modifier and Type | Method and Description |
---|---|
protected abstract void |
TestNode.execute(TestExec ts)
This is the method called by TestNode when all pre-processing related
to node execution is complete and LISA is prepared for the custom
node logic to be performed.
|
boolean |
TestCase.execute(TestExec ts,
java.lang.String nodeName)
This method, again only needed if you are not going to call executeTest(),
will execute the next TestNode in the test, then return.
|
boolean |
TestCase.executeNextNode(TestExec ts) |
void |
TestNode.executeNode(TestExec ts)
public void executeNode( TestExec ts )
Method that is called internally by LISA to execute a node.
|
java.lang.Object |
CustJavaNodeInterface.executeNodeLogic(TestExec ts,
java.util.Map params)
This is the biggy.
|
org.w3c.dom.Document |
TestExec.getLastResponseAsDocument()
When you need access to the last node response as an XML Document, use this
We cache into state the DOM so it will be parsed only once.
|
protected abstract java.util.Map<java.lang.String,?> |
DataSetImpl.getNextRecord(java.util.Map<java.io.Serializable,java.io.Serializable> testState)
This method return the next record in the order from the logical dataset.
|
java.lang.String |
RandSet.getRandom(TestExec ts)
Method generates a random from the list of possible values.
|
protected java.util.Map<java.lang.String,?> |
DataSetImpl.getRandomRecord(java.util.Map<java.io.Serializable,java.io.Serializable> testState)
This method is called to read a random record from the logical data set.
|
java.util.Map<java.lang.String,?> |
DataSet.getRecord(java.util.Map<java.io.Serializable,java.io.Serializable> testState)
This is the method called by the TestNode class in order to do a logical
read on the data set so that the specific property settings of this
data set record are reflected in the caller's state.
|
abstract java.util.Map<java.lang.String,?> |
DataSetImpl.getRecord(java.util.Map<java.io.Serializable,java.io.Serializable> testState)
This method is called to read a record from the logical data set, and
therefore must be implemented by the sublcass.
|
boolean |
FilterInterface.postFilter(TestExec ts)
This method is called on your filter after execution of the TestNode's
custom "execute()" method.
|
boolean |
FilterInterface.preFilter(TestExec ts)
This method is called by LISA after the currently executing TestNode
has prepared for the test Node's actual execution but before so doing.
|
void |
TestExec.startupTest()
If you do not want to call executeTest(), you can use this
method to prepare the Test Case object to start a test.
|
void |
CompanionInterface.testEnded(TestExec ts)
Thisi is the mirror of the testStarted method; the Test has completed execution,
including sending the final event that would normally be sent to all the TestEvent
listeners.
|
protected abstract void |
SimpleCompanion.testStarting(ParameterList params,
TestExec ts)
Called when LISA is about to execute the test.
|
void |
SimpleCompanion.testStarting(TestExec ts) |
void |
CompanionInterface.testStarting(TestExec ts)
This method is called by LISA after the TestCase has been loaded and
the state object for the given test execution has been initialized, but
before the test has begun.
|
void |
DataSet.validateData(java.util.Map<java.io.Serializable,java.io.Serializable> testState)
Called by the DataSetBaseInfoEditor to perform validation.
|
Modifier and Type | Method and Description |
---|---|
void |
StagedSuite.startTest()
Call when it's time to run the suite.
|
Copyright © 1998-2014 CA, Inc. All Rights Reserved.