Testing API: "Retired" TestItem "state"

[matepek]

There was a feature request: #115086

In case of the final API I don't know how to implement it. I cannot find the feature.
I guess it is removed. I think my users would love the feature.

Would you help me on this @connor4312 ?

[matepek]

Also there is a feature related to this which might worth to be considered. Test Explorer had an "auto-run" option.
If it is checked and there is a retired event about a test then a test-run will be created for those. (in case of test-explorer)

I can manually add option like this but it is a nice feature I believe.
A "Run retired/stale tests only" command can be useful also... maybe...

[connor4312]

The Test Explorer UI extension used retired states to drive autorun. I would instead like to have the extension drive its auto autorun (#134941), so retired states are no longer necessary for this use case and I'm not sure whether I want to bring them back.

[matepek]

The retired state basically an indicator in the tree view and the user can see if a test's result is outdated.
In case of c++ test executables I can detect the change of the moditime and mark all the tests coming from the executable as outdated. I love this feature. The way ho it does it that the retired tests' icons are 20% transparent I think. (Tooltip also could indicate it) Or maybe if I could just clear the state but that is less useful because it is nice to know what was the previous state of the test.

The auto-run is built upon this indeed. I can implement it easily if you don't wish to add it.
Regarding to this: It would be nice if we could contribute to the "..." menu. (adding new items. In this case: one with a checkbox)

[connor4312]

You can contribute to all test menus like any other menu 🙂 https://code.visualstudio.com/api/references/contribution-points#contributes.menus

[matepek]

Hello,
Any news on this front?

[matepek]

Hello,
Any news on this front?

[matepek]

Hello,
Any news on this front?

[xisui-MSFT]

Hi @connor4312, is there a way to mark some tests as outdated without auto rerun? In our extension, we would like to mark some tests as outdated in cases like some configs change, but we prefer not to do auto rerun since rebuilding the project may take a long time.