P4
The sense of this RFE is to provide ability to run all filters for particular test to see if it has been filtered out by some one reason or by a certain number of reasons.
The idea was to show reasons from all TestFilters from the stack that reject (and thus filter-out) particular test.
Example.
Stack of filters, established in the current TestSuite/Interview state and be following:
- Tests2Run filter. Filtered out reason is "Test is not selected"
- ExcludeListFilter. Filtered out reason is "Test appears in (Sun)Exclude List"
- KeywordsFilter. Filtered out reason is "Test doesn't match keywords".
- PriorStatusFilter. Filtered out reason is "Prior status is not selected".
- RelevantTestFilter ( == "applicability" filter). Filtered out reason can be "Test is not applicable for devide because PropertyA has value B".
- SeverityFilter (if "Specify Severities" == Yes). Filtered out reason is "Test severity is not selected".
Now imagine that com.sun.mytestpack.MyTestClass#myTestCase is such a test that it would be rejected by multiple filters:
- Tests2Run filter, because "mytestpack" is not selected.
- KeywordsFilter, because MyTestClass#myTestCase is automated while user entered "interactive" expression.
- RelevantTestFilter, because this MyTestClass#myTestCase is only relevant if PropertyA == A, while it's not true in configuration.
* In the Filtered Out tab, for this #myTestCase user will see only the first reason - "Test is not selected" from Tests2Run.
* User will say, OK - I'll go to configuration and select that test.
* Once he's back in the tree of tests - #myTestCase is still filtered out, but reason has changed - it's "Test doesn't match keywords" now.
* User is not happy because he wants to run this test! OK, he goes to Configuration and edits filter expression.
* Once he's back in the tree of tests - #myTestCase is still filtered out, but reason has changed to "Test is not applicable for devide because PropertyA has value B".
* Now user is really frustrated because he can't realize how long he would have to edit configuration to get this test active.
This RFE asks to provide a way to show reasons from ALL filters that currently filtering out this particular testcase.
Of course that because of performance reasons we should not apply all filters for the tree of tests if one filter has already excluded test. However, in the Filtered Out tab we can somehow provide user with possiblity to all reasons if there are multiple of them.
Example: make "Filtered Out Reason" table cell clickable. Once user clicks on it - run *all* TestFilters against selected test and show reasons from all matching filters.
The idea was to show reasons from all TestFilters from the stack that reject (and thus filter-out) particular test.
Example.
Stack of filters, established in the current TestSuite/Interview state and be following:
- Tests2Run filter. Filtered out reason is "Test is not selected"
- ExcludeListFilter. Filtered out reason is "Test appears in (Sun)Exclude List"
- KeywordsFilter. Filtered out reason is "Test doesn't match keywords".
- PriorStatusFilter. Filtered out reason is "Prior status is not selected".
- RelevantTestFilter ( == "applicability" filter). Filtered out reason can be "Test is not applicable for devide because PropertyA has value B".
- SeverityFilter (if "Specify Severities" == Yes). Filtered out reason is "Test severity is not selected".
Now imagine that com.sun.mytestpack.MyTestClass#myTestCase is such a test that it would be rejected by multiple filters:
- Tests2Run filter, because "mytestpack" is not selected.
- KeywordsFilter, because MyTestClass#myTestCase is automated while user entered "interactive" expression.
- RelevantTestFilter, because this MyTestClass#myTestCase is only relevant if PropertyA == A, while it's not true in configuration.
* In the Filtered Out tab, for this #myTestCase user will see only the first reason - "Test is not selected" from Tests2Run.
* User will say, OK - I'll go to configuration and select that test.
* Once he's back in the tree of tests - #myTestCase is still filtered out, but reason has changed - it's "Test doesn't match keywords" now.
* User is not happy because he wants to run this test! OK, he goes to Configuration and edits filter expression.
* Once he's back in the tree of tests - #myTestCase is still filtered out, but reason has changed to "Test is not applicable for devide because PropertyA has value B".
* Now user is really frustrated because he can't realize how long he would have to edit configuration to get this test active.
This RFE asks to provide a way to show reasons from ALL filters that currently filtering out this particular testcase.
Of course that because of performance reasons we should not apply all filters for the tree of tests if one filter has already excluded test. However, in the Filtered Out tab we can somehow provide user with possiblity to all reasons if there are multiple of them.
Example: make "Filtered Out Reason" table cell clickable. Once user clicks on it - run *all* TestFilters against selected test and show reasons from all matching filters.