P3
It appears that "Tests To Run" embedded filter aplies *after* all the filters contributed by the Parameters#getFilters().
By this reason we can see in "Filtered Out" tab different reasons for tests of testpacks that are unselected in "Tests to Run" panel: some of them (that passed all the specific filters) have reason "Test Name/Location not selected.", while some other tests (that do not pass all the specific filters) have a specific reason of some contributed filter.
It would be more logical and consistent to apply the "Tests To Run" filter before all the other filters since this filter is lightweight, and can filter out entire packages of tests.
Correspondiung Cr in JDTS is #6801155.
Note: this may be implemented in conjunction with Cr #6556984 (linked).
By this reason we can see in "Filtered Out" tab different reasons for tests of testpacks that are unselected in "Tests to Run" panel: some of them (that passed all the specific filters) have reason "Test Name/Location not selected.", while some other tests (that do not pass all the specific filters) have a specific reason of some contributed filter.
It would be more logical and consistent to apply the "Tests To Run" filter before all the other filters since this filter is lightweight, and can filter out entire packages of tests.
Correspondiung Cr in JDTS is #6801155.
Note: this may be implemented in conjunction with Cr #6556984 (linked).