|
If you were logged in you would be able to see more operations.
|
|
|
|
Test case configuration and options should optionally reside in an external configuration file, allowing the starting of rio infrastructure services to be done by the test framework, as well as the deployment of opstrings to be done for the test case
|
|
Description
|
Test case configuration and options should optionally reside in an external configuration file, allowing the starting of rio infrastructure services to be done by the test framework, as well as the deployment of opstrings to be done for the test case |
Show » |
made changes - 06/May/09 03:52 PM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
In Progress
[ 3
]
|
made changes - 23/Jun/09 04:48 PM
|
Status
|
In Progress
[ 3
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
made changes - 23/Jun/09 04:49 PM
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
|
Improvement
Closed
Major
Externalize test configuration, allowing RIo infrastructure to be started by test framework
groups: Discovery management groups to use
locators: Lookup locator strings (if any)
numCybernodes: The number of cybernodes to start (using discovery attributes provided)
numMonitors: The number of monitors to start (using discovery attributes provided)
numLookups: The number of lookup services to start (using discovery attributes provided)
opstring: The opstring to use
autoDeploy: Whether to automatically deploy the delcared opstring
testManager: The TestManager to create for the test case. If provided, the TestManager must extend the default TestManager. If not provided, and instance of: org.rioproject.test.TestManager(true) is created
Each test case is scoped by the testcase's classname, sans the package name. For example: org.rioproject.test.deploy.SimpleDeployTest is references in the test configuration file as:
SimpleDeployTest { ... }