Expose org.springframework.test.web.servlet.assertj.DefaultMvcTestResult or provide factory method to create org.springframework.test.web.servlet.assertj.MvcTestResult

[zeldigas]

MockMvcTester is really great, but it is currently implemented in pretty self-contained way - you must use it for all stages - from making request to doing responses.

I have a scenario where i want to start directly with fluent assertions (request phase is done in internal project specific code that eventually can return ResultAction/MvcResult). Unfortunatelly all constructors are package local so there is no good way (instead of hacky-style creating class in spring's package) to do the part that is currently done inside org.springframework.test.web.servlet.assertj.MockMvcTester#perform:

//the part that I'd like to do
new DefaultMvcTestResult(mvcResult, null, this.converterDelegate);

Can you consider exposign it or suggesting what can be the option without changing existing Spring codebase?

[rstoyanchev]

So you have some existing code that performs the request via MockMvc and returns an MvcResult? Is it not be feasible to re-write that code to use MockMvcTester instead, or if not could you elaborate on the challenge with that?

It would be a bit odd to create a method that takes MvcResult suggesting split use between the request phase with static imports, and the response phase with fluent assertions.

[snicoll]

I am not quite sure I understand what the problem is. If your request phase is self contained, you should go through MockMvc#perform(RequestBuilder) right? If so, there is the same method on MockMvcTester.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.