
|
If you were logged in you would be able to see more operations.
|
|
|
CubicTest
Created: 31/Jul/08 01:25 PM
Updated: 15/Aug/08 05:44 PM
|
|
| Component/s: |
Core
|
| Affects Version/s: |
1.8.6
|
| Fix Version/s: |
1.8.11
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
When running a test with multiple subtest levels, it's important to be able to identify which steps were executed and which where not. However, custom test steps are only maked in green when their respectives tests are in foreground. Since our tests are almost fully based on custom components, it becomes hard for testers to identify more precisely the failure point without this information.
|
|
Description
|
When running a test with multiple subtest levels, it's important to be able to identify which steps were executed and which where not. However, custom test steps are only maked in green when their respectives tests are in foreground. Since our tests are almost fully based on custom components, it becomes hard for testers to identify more precisely the failure point without this information. |
Show » |
|