jtr.runners
Class JUnitFacadeRunner

java.lang.Object
  jtr.runners.AbstractRunnerAncestor
      jtr.runners.JUnitFacadeRunner

All Implemented Interfaces:

java.lang.Runnable, IRunner, IRunnerClean, IRunnerParameterized, IRunnerPooled

public class JUnitFacadeRunner
extends AbstractRunnerAncestor

Since:

5.0

Version:

5.0

Author:

frusso

Nested Class Summary

static class

JUnitFacadeRunner.JUnitFacadeRunnerException

Field Summary

Fields inherited from class jtr.runners.AbstractRunnerAncestor

logger

Constructor Summary

JUnitFacadeRunner()

Method Summary

void	cleanupResources() This method has to be implemented by all concrete IRunner implementations for performing resource clean-up operations (closing connections, closing files, etc.). In the current release of JTR, the framework will start the resource clean-up session only upon completion of the last epoch and once all the IRunners have been put back into the pool. For an IRunner extending the AbstractJMSRunner abstract class, the injection of all the JMS administered objects and connections will happen only once, before the first run of the first epoch is started. This is for not wasting both time and resources for gathering always the same resources every time a new run has to be executed.
void	receiveFailureNotification(java.lang.Throwable t, java.lang.String msg) Callback method for receiving notification of occourred errors.
protected void	specializedBeforeRunTest() This method allows more specialized subclasses to perform preparatory activities right before the actual test is launched. Note: implementations of this method must always be final.
void	test() This method starts the test logic.

Methods inherited from class jtr.runners.AbstractRunnerAncestor

addMessage, afterTest, beforeTest, clean, enrichOutcome, getCurrentRun, getDefaultName, getEnterprise, getEpoch, getFailures, getFqn, getInstanceCount, getInstanceID, getName, getOutcomeFactory, getParameters, getParamsAssigner, getPool, getRuns, getSleepTime, getStatFunction, getSuccesses, getTestOutcomeTable, getUserMessage, handleFailure, run, setCurrentRun, setEnterprise, setEpoch, setFqn, setInstanceCount, setInstanceID, setName, setOutcomeFactory, setParameters, setParamsAssigner, setPool, setRuns, setSleepTime, setStatFunction, setTestCompletionListener, setTestOutcomeTable

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

JUnitFacadeRunner

public JUnitFacadeRunner()

Method Detail

specializedBeforeRunTest

protected final void specializedBeforeRunTest()
                                       throws java.lang.Throwable

Description copied from class: AbstractRunnerAncestor

This method allows more specialized subclasses to perform preparatory activities right before the actual test is launched.

Note: implementations of this method must always be final.

Specified by:

specializedBeforeRunTest in class AbstractRunnerAncestor

Throws:

java.lang.Throwable

test

public void test()
          throws java.lang.Throwable

Description copied from interface: IRunner

This method starts the test logic.

Throws:

java.lang.Throwable

receiveFailureNotification

public void receiveFailureNotification(java.lang.Throwable t,
                                       java.lang.String msg)

Description copied from interface: IRunner

Callback method for receiving notification of occourred errors.

Parameters:

t - Throwable

msg - String

cleanupResources

public void cleanupResources()

Description copied from interface: IRunnerPooled

This method has to be implemented by all concrete IRunner implementations for performing resource clean-up operations (closing connections, closing files, etc.).
In the current release of JTR, the framework will start the resource clean-up session only upon completion of the last epoch and once all the IRunners have been put back into the pool.
For an IRunner extending the AbstractJMSRunner abstract class, the injection of all the JMS administered objects and connections will happen only once, before the first run of the first epoch is started.
This is for not wasting both time and resources for gathering always the same resources every time a new run has to be executed.

See Also:

AbstractRunnerAncestor.clean()