wac | WebAssembly interpreter in C | Binary Executable Format library

You should move you Dtos to the independent files making them regular or make them static within the controller. Actually it's an old-known feature. Here is an explanation

UPD

I've reproduced your case. The problem is absolutely easy - you don't read the file creating the File instance. To read the file do this:

You can load a html table directly into pandas using read_html, no need to use BeautifulSoup. You can then process the dataframe by removing the top header row and the mid-table header rows:

I'm not totally sure because you didn't show an actual test but I guess you should use @MockBean and not @Mock.

@Mock is used for plain Unit Test when you do the dependency injection yourself. @MockBean is used for integration tests when you want to use your Mock as a regular Bean.

Long story shot. Try this:

I don't think you can put a SAS token in an Authorization header. I can't find any relevant sample, so I used the Using the Azure.Storage.Blob C# client library from NuGet to do this

Uff, okay, so apparently if I need to configure WebAppContext, I can just add jetty-web.xml to my WEB-INF folder and Jetty will automatically use it.

So in the end my jetty-web.xml looks like this:

You can use @MockBean instead of @Mock, it will export the field as a bean in the spring context.

Nunyet, the problem is that although you are configuring H2 to store the information in memory, from the point of view of Spring and Spring Boot, you have the same database system, the same transactions, the same entities, ... in summary, the same behavior as if you were using H2 and storing the information on the filesystem or other different database system.

If you do not mock your repository, Spring will try to create the actual UserRepository and look forward the required dependencies to do so, like entityManagerFactory in your case.

Probably your problem could be related with the following line:

I see several reasons why this does not work :

A - @Mock alone is not enough to initialize a mock. You need either :

• Call MockitoAnnotations.initMocks() in setup
• Remove @Mock and call Mockito.mock(UserRepository.class) in setup

However I don't think this will be enough, which brings me to :

B - Your controller looks managed by spring, whereas your mocked AutorisationService is not.

I am assuming there that your controller uses an AutorisationService supposedly injected by spring.

You have several options here :

• Option 1 - Don't use spring at all for your test, and manage your controller and service with mockito. This should look like :