Package | Description |
---|---|
com.itko.lisa.coordinator | |
com.itko.lisa.stats | |
com.itko.lisa.test | |
com.itko.lisa.testing |
Modifier and Type | Interface and Description |
---|---|
interface |
SuiteCoordinator
This is the sub interface used for staging suites.
|
interface |
TestCoordinator
This is the sub interface to Coordinator that specifically works with staged tests.
|
Modifier and Type | Class and Description |
---|---|
class |
com.itko.lisa.coordinator.BaseCoordinator |
Modifier and Type | Method and Description |
---|---|
Coordinator |
TestRegistry.findCoordinator(java.lang.String locator)
This method is used to locate a coordinator by its locator descriptor.
|
Coordinator |
ReportGenerator.getCoordinator()
Our implementations will need this to do interesting reports.
|
Modifier and Type | Method and Description |
---|---|
java.util.Hashtable<java.lang.String,Coordinator> |
CoordinatorServer.getCoordinators()
Returns a cloned copy of all the currently maintained Coordinators running
in this CoordinatorServer.
|
Modifier and Type | Method and Description |
---|---|
static void |
ReportGenerator.attachEventConsumers(Coordinator c,
java.util.List consumers)
Used internally once a test is staged to make sure they are all hooked into the Coordinator
|
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.
|
protected void |
ReportGenerator.setCoordinator(Coordinator c)
Called internally to give Report Generators the handle to the Coordinator
|
static TestCoordinator |
TestRunner.stageTest(Coordinator parent,
com.itko.lisa.model.mar.ModelArchive mar)
This method will stage a test with the given parameters onto the network and
return the Coordinator that can be used to start, query, and stop the test.
|
static TestCoordinator |
TestRunner.stageTest(Coordinator parent,
com.itko.lisa.model.mar.ModelArchive mar,
com.itko.lisa.test.Project project) |
static TestCoordinator |
TestRunner.stageTest(Coordinator parent,
RunInfo stage,
java.lang.String testCaseFileName,
TestCase test,
java.lang.String csName)
This method will stage a test with the given parameters onto the network and
return the Coordinator that can be used to start, query, and stop the test.
|
static TestCoordinator |
TestRunner.stageTest(Coordinator parent,
java.lang.String testRun,
java.lang.String testName,
java.lang.String configFile,
java.lang.String csName)
This method will stage a test with the given parameters onto the network and
return the Coordinator that can be used to start, query, and stop the test.
|
static TestCoordinator |
TestRunner.stageTest(Coordinator parent,
java.lang.String testRun,
java.lang.String testName,
java.lang.String configFile,
java.lang.String csName,
java.util.List<java.lang.String> extras)
This method will stage a test with the given parameters onto the network and
return the Coordinator that can be used to start, query, and stop the test.
|
static TestCoordinator |
TestRunner.stageTestByMAR(Coordinator parent,
java.lang.String marFileLocation,
java.lang.String csName)
This as of 5.1 will become probably the most commonly used of the ways to stage tests with TestRunner; we take a
reference to a mar file and we read it and stage it to a possibly remote Coordinator.
|
static TestCoordinator |
TestRunner.stageTestFromMARInfo(Coordinator parent,
java.lang.String marInfoFileName,
java.lang.String csName)
This allows for the staging of a test case by way of a descriptive MAR info file.
|
Modifier and Type | Method and Description |
---|---|
Coordinator |
MetricCollector.getCoordinator()
This method is of interest to subclasses that need to get a handle to the Coordinator
for this test
|
Modifier and Type | Method and Description |
---|---|
void |
MetricCollector.setCoordinator(Coordinator c)
This method is generally called by the TestManager when setting up metrics to be
used.
|
Modifier and Type | Method and Description |
---|---|
Coordinator |
TestExec.getCoordinator() |
Modifier and Type | Method and Description |
---|---|
void |
TestCase.fixupRemoteReferences(Coordinator c)
if we haven't yet resolved remote connectivity to Coordinator assets, ala the DSM, do it now
|
Modifier and Type | Class and Description |
---|---|
class |
StagedSuite
StagedSuite
This is a Coordinator for test suites.
|
Modifier and Type | Method and Description |
---|---|
Coordinator |
RegressionRunner.getRunningCoordinator()
If this test is currently running, this is the Coordinator responsible for it
|
Copyright © 1998-2014 CA, Inc. All Rights Reserved.