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 Summary
Modifier and TypeFieldDescriptionstatic final String
Application exception : "Application Exception"static final String
"Application forcibly shut down"static final String
"Shutdown interrupted"static final String
"Condition failed -skipping tests"static final String
Teardown exception : "Teardown Exception"static final String
"Overriding previous definition of "Fields inherited from class org.apache.tools.ant.ProjectComponent
description, location, project
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionvoid
addApplication
(Sequential sequence) Add an application.void
Add a block.void
addReporting
(Sequential sequence) set reporting sequence of tasks.void
addSetup
(Sequential sequence) Add a setup sequence.void
addTeardown
(Sequential sequence) set teardown sequence of tasks.void
addTests
(Sequential sequence) add tests.Add a condition element.void
execute()
Run the functional test sequence.Get the application exception.Get the task exception.Get the teardown exception.Get the test exception.protected void
ignoringThrowable
(String type, Throwable thrown) log that we are ignoring something rather than rethrowing it.protected void
Now faults are analysed.void
setFailOnTeardownErrors
(boolean failOnTeardownErrors) Set the failOnTeardownErrors attribute.void
setFailureMessage
(String failureMessage) Set the failureMessage attribute.void
setFailureProperty
(String failureProperty) Set the failureProperty attribute.void
setShutdownTime
(long shutdownTime) Set the shutdownTime attribute.void
setShutdownUnit
(WaitFor.Unit unit) Set the shutdownunit attribute.void
setTimeout
(long timeout) Set the timeout attribute.void
setTimeoutUnit
(WaitFor.Unit unit) Set the timeoutunit attribute.Methods inherited from class org.apache.tools.ant.Task
bindToOwner, getOwningTarget, getRuntimeConfigurableWrapper, getTaskName, getTaskType, getWrapper, handleErrorFlush, handleErrorOutput, handleFlush, handleInput, handleOutput, init, isInvalid, log, log, log, log, maybeConfigure, perform, reconfigure, setOwningTarget, setRuntimeConfigurableWrapper, setTaskName, setTaskType
Methods inherited from class org.apache.tools.ant.ProjectComponent
clone, 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_EXCEPTION
Application exception : "Application Exception"- See Also:
-
TEARDOWN_EXCEPTION
-
-
Constructor Details
-
Funtest
public Funtest()
-
-
Method Details
-
createCondition
Add a condition element.- Returns:
ConditionBase
.- Since:
- Ant 1.6.2
-
addApplication
Add an application.- Parameters:
sequence
- the application to add.
-
addSetup
Add a setup sequence.- Parameters:
sequence
- the setup sequence to add.
-
addBlock
-
addTests
-
addReporting
set reporting sequence of tasks.- Parameters:
sequence
- a reporting sequence to use.
-
addTeardown
set teardown sequence of tasks.- Parameters:
sequence
- a teardown sequence to use.
-
setFailOnTeardownErrors
public void setFailOnTeardownErrors(boolean failOnTeardownErrors) Set the failOnTeardownErrors attribute.- Parameters:
failOnTeardownErrors
- the value to use.
-
setFailureMessage
Set the failureMessage attribute.- Parameters:
failureMessage
- the value to use.
-
setFailureProperty
Set the failureProperty attribute.- Parameters:
failureProperty
- the value to use.
-
setShutdownTime
public void setShutdownTime(long shutdownTime) Set the shutdownTime attribute.- Parameters:
shutdownTime
- the value to use.
-
setTimeout
public void setTimeout(long timeout) Set the timeout attribute.- Parameters:
timeout
- the value to use.
-
setTimeoutUnit
Set the timeoutunit attribute.- Parameters:
unit
- the value to use.
-
setShutdownUnit
Set the shutdownunit attribute.- Parameters:
unit
- the value to use.
-
getApplicationException
Get the application exception.- Returns:
- the application exception.
-
getTeardownException
Get the teardown exception.- Returns:
- the teardown exception.
-
getTestException
-
getTaskException
-
execute
Run 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:
execute
in classTask
- Throws:
BuildException
- if something was caught during the run or teardown.
-
processExceptions
protected 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
-