|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||
Agent capabilities.
All agents in the alert framwork must be JUnit testcases. To be able to participate in an alert run they must also implement the extended Agent interface. This is because the tests in agent are dynamicall instantiated an one testcase class may be used for multiple alerts. It must therefore be possible to give an instance of a testcase a unique name that is different from its class name and test method. It must also be possible to give it a unique set of properties.
An agent will be given its name from the alert configuration file. It will also be given al the properties defined for that particular instance.
Even if an Agent is a JUnit test case it should normally not throw an assert through the JUnit assert methods, but instead throw one if AlertError or AlertWarning, since these are threade specially by the AlertReporter.
The allready avaliable agens are in org.backsource.alert.agent.
| Method Summary | |
void |
initialize(java.lang.String agentName,
java.util.Properties prop)
Initialize the agent with a unique describing name and its properties. |
| Methods inherited from interface junit.framework.Test |
countTestCases, run |
| Method Detail |
public void initialize(java.lang.String agentName,
java.util.Properties prop)
throws java.lang.Exception
java.lang.Exception
|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||