Test Execution Filtering

[colross]

Hi - I have a question. I am unsure if my understanding of the feature is incorrect, or if the feature does not quite work correctly.
I am running the 1.9 Beta 6
When you go to the "Test Execution" link, you get a coloured display on the left. (Incidentally, this is one of my favourite features).
The colouration shows by default for the "build to execute" that you have selected in the Settings area. When you change the "build to execute" the colouration changes to match the new build that yo have selected.
Within the Filter section, there is a possibility to select Result [ANY] on "latest execution", or "ALL builds" and other options.
My expectation here is that the colouration would now show all executions, so that I can see at a glance what is missing (regardless of the "build to execute")
This is not the case, however. The colouration strictly follows the build in the "Settings" area.
Is my expectation incorrect? If so, what is the purpose of this filter, as it seems to have no effect?

Cheers
Colin

[Julian]

your analysis is absolutely correct.

filters do only serve the purpose of reducing the amount of test cases shown

example of how to use the filter:

you want to run all tests that failed for a prior build with the newest build.

you set the filter to:
Result: failed
on specific build:
1.0

-> tree will show all test cases that failed for build 1.0 BUT coloring of test cases stays the same!

[colross]

Thanks for the info.
If I were to raise an enhancement on this (it is a brilliant way of getting insight into where exactly you are), what is the likelihood that it would be implemented?

[Julian]

very low as people do not like changes here.

see our last try to change colors: http://mantis.testlink.org/view.php?id=3450

the only alternativ would be another setting allowing to influence the coloring.

something like
color tree according to
- last execution for all builds
- last execution for build chosen for execution
- ...

[slbogdan]

Hi, i have a problem with testcase execution filtering too.

I am using 1.9 build and after executing some testcases I wanted to filter it using filter Result. The problem is whatever value I set for Result filer all testcases are shown.

Someone else had same problem?

Thank you!

[ansar]

My testers are having the same problem. We have multiple builds per release cycle.

When you use the filter:

Result=Not Run
on ANY Build

I would expect to only see Test Cases that have not been run at all listed, but I am still seeing all test cases listed in the Tree View.

Is this a bug or expected behavior?