rediscovery of tests which where not changed should not become unknown (?)

[chanansh]

In respect to #9606, in my humble opinion, I think it is very annoying to lose all your test status just because you have added one test. So, assume that you have written 100 tests, 80 passes, 20 failed. You are adding the 101 test and then you are losing which tests are yet to be solved (the 20/100 or more correctly 20/101 now that you have a new test.). If testing takes time, you need now to wait an hour or so to get again the list of failed tests. I suggest a checkbox which "keeps" the state and then "refresh" only add new/remove tests

@isidorn I feel that if test discovery is triggered, it should refresh the state of the tests (and that's also the reason why we chose the "refresh" icon for this). If the user makes changes and triggers test discovery again, retaining the previous state will show now an incorrect state. If the name of the test changes as well as its result, what would be the expected state, in this case?
Personally, I think "unknown" makes sense for all of these cases.
Anyway, tagging it as "needs decision" so I can talk to the team about it 😊

Originally posted by @luabud in #9606 (comment)

[isidorn]

Idealy in the future the test view would use our newly introduced test view by @connor4312 instead of a custom solution

[karthiknadig]

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

[luabud]

Closing in favour of #15750