controllertest | Portable N64 Controller Tester

Cucumber isn't used for unit tests because the main benefit of Cucumber is to be able to express the behaviour you are examining using abstract high level natural language. That sort of language does not have such a good fit with unit tests, which should be much more focused on detail of how a unit behaves.

If you use low level of abstractions in cucumber and document HOW things are done you end up with verbose scenarios that quickly become unwieldy and difficult to work with.

The idea of one testing tool to test (rule) them all is initially very appealing. I was strongly drawn to it for a while. With greater experience of cuking it became clear this idea is flawed. Unit test tools are much better for writing unit tests, its easy to loop, mock and do more exhaustive testing. If you implement them correctly they will always run much faster as well.

This idea of using different tools at different scales is nothing new, it applies to almost every human endeavour. Testing is no different. Use Cucumber for describing (ideally driving) high level behaviour of a system/application. Use unit testing to smaller detailed testing of units.

You do not have content in the request

You are not sending the required parameters (the parameters annotated with @RequestParam) to the method. By default they are all required. If not present Spring blocks the request with missing arguments.

Example of sending parameters:

I added mocking the decoder in the test as

You need to extend the WebTestCase provided by Symfony, not the default TestCase provided by PHPUnit.

Here is an example for a similar test you are trying to write:

I don't think @Karate.Test is compatible with @SpringBootTest so you may need to figure this out on your own.

Here's a tip - the Karate JUnit support is just a convenience which is not mandatory to use. You may be able to create reasonable test suites that play well with @SpringBootTest using the Karate "core" Runner class.

For a detailed explanation, see: https://stackoverflow.com/a/65578167/143475

Check if Redis port is available or not. if not, try to assign a different port

The problem seems to be that you have two entities with a relation and try to delete one of them as the problem says:

Referential integrity constraint violation: "FK3YM8KNF15YHIGFNBABIYLPY1C: PUBLIC.USER_OTP_DATA FOREIGN KEY(CUSTOMER_ID) REFERENCES PUBLIC.USERS(CUSTOMER_ID) (1)"; SQL statement:

There either is an automated SQL statement being executed or one of your methods does as the very top of the stacktrace says:

org.springframework.dao.DataIntegrityViolationException: could not execute statement

And a bit further, there is a reference to your code:

You can reference Spring MVC Test Framework - Unsupported Media Type

You may be missing @EnableWebMvc annotation in your controller.

EDIT - for Comment:

Instead of