Why do I have to use @ContextConfiguration without a ContextConfiguration to load the AppContext?

[round pecan]

<@&1004656351647117403> please have a look, thanks.

[round pecan]

While you are waiting for getting help, here are some tips to improve your experience:

Code is much easier to read if posted with syntax highlighting and proper formatting.

If nobody is calling back, that usually means that your question was not well asked and hence nobody feels confident enough answering. Try to use your time to elaborate, provide details, context, more code, examples and maybe some screenshots. With enough info, someone knows the answer for sure.

Don't forget to close your thread using the command </help-thread close:1027500463647621170> when your question has been answered, thanks.

[paper pivot]

Mind sharing the whole exception?

[pseudo skiff]

Here is the whole exception for the error when leaving out the @ ContextConfiguration. I know I could just define all the beans as @MockBeans but that isn't really a better solution since it should be able to load the application context without me having to declare every dependency as a @MockBean. This error doesn't occur when using the @ ContextConfiguration but as I said in the question then I get a 204 which shouldn't be possible (yes in my previous tests it worked and I only changed a few dependencies and you can see the code, it is correct if everything is set up correctly what I don't think)

[round pecan]

I uploaded your attachments as Gist.