Add @WebEndpointTest for testing custom actuator web points

[manderson23]

It would be convenient if, similar to @WebMvcTest, there was a @WebEndpointTest annotation to support testing custom @WebEndpoint implementations.

[snicoll]

@manderson23 can you expand on what you are expecting exactly? Is that an web-specific test style where you could use MockMvc to contact the endpoint? You can't use MockMvc with a reactive-based app so that's not really realistic.

We use a custom rule to make sure each endpoint runs consistently with MVC, WebFlux and Jersery. I am not sure that's what you're after.

[manderson23]

@snicoll OK in my case I'm MVC only so I'd be happy to make my own rule. I did look at your tests and seen the custom rule there. Would it be feasible and/or useful to make that part of the public API?

[wilkinsona]

I'm reluctant to make WebEndpointRunners public as I don't want to be affected by the constraints that it would introduce. Being able to make breaking changes to the runner whenever we like is rather useful. Unfortunately, I don't think we have time in 2.0 to revisit our runner to get it into a state where it's ready to be public.

[wilkinsona]

We discussed this a bit more today, and our feeling is that you should either just unit test your endpoint and trust the infrastructure to do what it claims to do, or you can create a full-blown integration test and call the endpoint using TestRestTemplate, for example.