
| Key: |
WET-249
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Raghu Venkataramana
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
WET
Created: 02/Oct/06 03:13 AM
Updated: 02/Apr/07 10:16 PM
|
|
| Component/s: |
Test controller
|
| Affects Version/s: |
0.8.0,
0.9.8_beta1,
0.9.8 Final
|
| Fix Version/s: |
1.2
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Currently the object depot path can be set on per test definition level by setting:
object_repository=My_repos_path
For many applications, typically there is one object depot file that is most commonly used. Instead of having to set this path in each test definition(and in future maintaining it), it would be nice if one could define this value at a global value.
The behavior should be:
1) Test Definition value should override the value set in the global configuration
2) Test Definition should also allow the global setting to be ignored. This is required in cases where you dont want to use an object depot for some select test cases but there is a global value defined.
The design should accomadate the 'support for multiple object depots' when implemented:
1) Default behavior is to add the object depots defined in the test definition to the ones defined in the global configuration
2) There should be an option to ignore the global setting totally and use only the one defined in the test definition (There may be nothing spl. required here as item(2) in the previous comment will take care of this)
|
|
Description
|
Currently the object depot path can be set on per test definition level by setting:
object_repository=My_repos_path
For many applications, typically there is one object depot file that is most commonly used. Instead of having to set this path in each test definition(and in future maintaining it), it would be nice if one could define this value at a global value.
The behavior should be:
1) Test Definition value should override the value set in the global configuration
2) Test Definition should also allow the global setting to be ignored. This is required in cases where you dont want to use an object depot for some select test cases but there is a global value defined.
The design should accomadate the 'support for multiple object depots' when implemented:
1) Default behavior is to add the object depots defined in the test definition to the ones defined in the global configuration
2) There should be an option to ignore the global setting totally and use only the one defined in the test definition (There may be nothing spl. required here as item(2) in the previous comment will take care of this) |
Show » |
|