Class Funtest
java.lang.Object
org.apache.tools.ant.ProjectComponent
org.apache.tools.ant.Task
org.apache.tools.ant.taskdefs.optional.testing.Funtest
- All Implemented Interfaces:
- Cloneable
Task to provide functional testing under Ant, with a fairly complex workflow of:
 
- Conditional execution
- Application to start
- A probe to "waitfor" before running tests
- A tests sequence
- A reporting sequence that runs after the tests have finished
- A "teardown" clause that runs after the rest.
- Automated termination of the program it executes, if a timeout is not met
- Checking of a failure property and automatic raising of a fault (with the text in failureText) if test shutdown and reporting succeeded
- Since:
- Ant 1.8
- 
Field SummaryFieldsModifier and TypeFieldDescriptionstatic final StringApplication exception : "Application Exception"static final String"Application forcibly shut down"static final String"Shutdown interrupted"static final String"Condition failed -skipping tests"static final StringTeardown exception : "Teardown Exception"static final String"Overriding previous definition of "Fields inherited from class org.apache.tools.ant.ProjectComponentdescription, location, project
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionvoidaddApplication(Sequential sequence) Add an application.voidAdd a block.voidaddReporting(Sequential sequence) set reporting sequence of tasks.voidaddSetup(Sequential sequence) Add a setup sequence.voidaddTeardown(Sequential sequence) set teardown sequence of tasks.voidaddTests(Sequential sequence) add tests.Add a condition element.voidexecute()Run the functional test sequence.Get the application exception.Get the task exception.Get the teardown exception.Get the test exception.protected voidignoringThrowable(String type, Throwable thrown) log that we are ignoring something rather than rethrowing it.protected voidNow faults are analysed.voidsetFailOnTeardownErrors(boolean failOnTeardownErrors) Set the failOnTeardownErrors attribute.voidsetFailureMessage(String failureMessage) Set the failureMessage attribute.voidsetFailureProperty(String failureProperty) Set the failureProperty attribute.voidsetShutdownTime(long shutdownTime) Set the shutdownTime attribute.voidsetShutdownUnit(WaitFor.Unit unit) Set the shutdownunit attribute.voidsetTimeout(long timeout) Set the timeout attribute.voidsetTimeoutUnit(WaitFor.Unit unit) Set the timeoutunit attribute.Methods inherited from class org.apache.tools.ant.TaskbindToOwner, getOwningTarget, getRuntimeConfigurableWrapper, getTaskName, getTaskType, getWrapper, handleErrorFlush, handleErrorOutput, handleFlush, handleInput, handleOutput, init, isInvalid, log, log, log, log, maybeConfigure, perform, reconfigure, setOwningTarget, setRuntimeConfigurableWrapper, setTaskName, setTaskTypeMethods inherited from class org.apache.tools.ant.ProjectComponentclone, getDescription, getLocation, getProject, setDescription, setLocation, setProject
- 
Field Details- 
WARN_OVERRIDING
- 
APPLICATION_FORCIBLY_SHUT_DOWN"Application forcibly shut down"- See Also:
 
- 
SHUTDOWN_INTERRUPTED
- 
SKIPPING_TESTS
- 
APPLICATION_EXCEPTIONApplication exception : "Application Exception"- See Also:
 
- 
TEARDOWN_EXCEPTION
 
- 
- 
Constructor Details- 
Funtestpublic Funtest()
 
- 
- 
Method Details- 
createConditionAdd a condition element.- Returns:
- ConditionBase.
- Since:
- Ant 1.6.2
 
- 
addApplicationAdd an application.- Parameters:
- sequence- the application to add.
 
- 
addSetupAdd a setup sequence.- Parameters:
- sequence- the setup sequence to add.
 
- 
addBlock
- 
addTests
- 
addReportingset reporting sequence of tasks.- Parameters:
- sequence- a reporting sequence to use.
 
- 
addTeardownset teardown sequence of tasks.- Parameters:
- sequence- a teardown sequence to use.
 
- 
setFailOnTeardownErrorspublic void setFailOnTeardownErrors(boolean failOnTeardownErrors) Set the failOnTeardownErrors attribute.- Parameters:
- failOnTeardownErrors- the value to use.
 
- 
setFailureMessageSet the failureMessage attribute.- Parameters:
- failureMessage- the value to use.
 
- 
setFailurePropertySet the failureProperty attribute.- Parameters:
- failureProperty- the value to use.
 
- 
setShutdownTimepublic void setShutdownTime(long shutdownTime) Set the shutdownTime attribute.- Parameters:
- shutdownTime- the value to use.
 
- 
setTimeoutpublic void setTimeout(long timeout) Set the timeout attribute.- Parameters:
- timeout- the value to use.
 
- 
setTimeoutUnitSet the timeoutunit attribute.- Parameters:
- unit- the value to use.
 
- 
setShutdownUnitSet the shutdownunit attribute.- Parameters:
- unit- the value to use.
 
- 
getApplicationExceptionGet the application exception.- Returns:
- the application exception.
 
- 
getTeardownExceptionGet the teardown exception.- Returns:
- the teardown exception.
 
- 
getTestException
- 
getTaskException
- 
executeRun the functional test sequence.This is a fairly complex workflow -what is going on is that we try to clean up no matter how the run ended, and to retain the innermost exception that got thrown during cleanup. That is, if teardown fails after the tests themselves failed, it is the test failing that is more important. - Overrides:
- executein class- Task
- Throws:
- BuildException- if something was caught during the run or teardown.
 
- 
processExceptionsprotected void processExceptions()Now faults are analysed.The priority is - testexceptions, except those indicating a build timeout when the application itself failed. (Because often it is the application fault that is more interesting than the probe failure, which is usually triggered by the application not starting.)
- Application exceptions (above test timeout exceptions)
- Teardown exceptions -except when they are being ignored
- Test failures as indicated by the failure property
 
- 
ignoringThrowable
 
-