Connor Peet

> You could also make a (VSCode) feature request for some other UI indication, such as graying out the test. I'm hesitant to do this since [publish-only controllers](https://code.visualstudio.com/api/extension-guides/testing#publishonly-controllers) can exist...

I'm not clear on what you're asking for here. What is the benefit of "a different exception", where would it come from?

I see. Currenly this library doesn't have anything analogous to that, and `onGiveUp` is just a 'notification', not a handler. This should not be hard to implement by hand in...

Would be happy to add this. PR's welcome if you're up for it.

Just looking through the things you mention... - Pipelines: reading through the docs, I'm not sure how these are much different from the [`wrap`](https://github.com/connor4312/cockatiel#wrappolicies) function that cockatiel provides. Are there...

The `execute` will either return the successful result or propagate the last error the `retryPolicy` encountered. If you want to observe errors thrown from the circuit breaker, or failures during...

We could have a setting for this; if more users request it we could go that direction. An extension could also manually run the `testing.clearTestResults` command.

That's right--unfortunately no command to clear a specific controller's output.

Yea, I think some `testing.historyEnabled` would be the right solution here. I would want to see if there's interest from more people here before taking the time to implement it...

sounds good 🙂