Captor | Automatic subtlitles for deaf people using Google Cardboard | Augmented Reality library

You have some service that you want to test. There are some inner dependencies and you want to check their calls. For the typical service's unit test you usually should mock all of the inner dependencies and their behaviors like that:

My question is, do you think this method is fine to get negative raw value ?

Code below likely "works", yet relies on implementation defined behavior. (and UB if int is 16-bit)

The two methods may be identical in their defined behavior, depending on the type of rawTemp, which we are not shown. However, neither is a generally correct way to decode an int16_t value from two eight-bit bytes.

Considering this code first:

Edited to match edited code in question

To transfer your accelerometer data you could do something similar to the BatteryMonitor example:

Use notifications on your characteristic to allow your smartphone to receive changes without constantly reading manually. Readout and update accelerometer data constantly while central is connected.

The error says that PLX-DAQ won't accept ASCII characters < 10 or > 200.

\t, horizontal tab is decimal 9. Make sure you only send characters which are decimal 10-200 in the ASCII table.

https://en.wikipedia.org/wiki/ASCII

From the PLX-DAQ manual:

• For simple error checking, PLX-DAQ will indicate an error anytime that a string containing characters < ASCII 10 or > ASCII 200 is received.
• Values of ASCII 10 (Line Feed) are replaced with ASCII 13 (Carriage Return) prior to processing.

I suggest you use comma instead of horizontal tab to separate the values.

Indeed, the @Captor annotation only works when you enable the MockitoExtension.

But you can also manually initialize the ArgumentCaptor without the @Captor annotation:

@WebFluxTest is intended for testing the slice of an application that's using WebFlux's annotation-based programming model. It includes @Controller beans (among others) but not RouterFunction beans. The value attribute of @WebFluxTest should be used to identify a specific @Controller that you want to test rather than testing all @Controller beans. @WebFluxTest({ RegistrationHandler.class }) doesn't look right as I don't think RegistrationHandler is a controller.

You should use @SpringBootTest or @Import your RouterFunction implementation instead, as noted in the Spring Boot reference documentation:

@WebFluxTest cannot detect routes registered via the functional web framework. For testing RouterFunction beans in the context, consider importing your RouterFunction yourself via @Import or using @SpringBootTest.

The problem is that the pageable argument of the getItemsBasedOnCategoryID is non-nullable, while the return type of the ArgumentCaptor.capture is a platform type, which is considered by the Kotlin compiler as possibly nullable (and actually capture() returns null, that's how Mockito works). In such a case, the compiler generates null checks, when the type is used. You can see it in the decompiled code of your test:

You should test if the returned userId has the expected value. Tell the userMapper mock to return a specific value and assert that the userService returned it as well.