http-status-codes | PHP List of HTTP status codes | Application Framework library

To prevent duplicate logging in this case, you can place UseSerilogRequestLogging() before UseStatusCodePagesWithReExecute() in your Configure method:

Even if the status code is 429 or 500 or 503, you're going to flow off the bottom of the if/elif/elif sequence and right into the raise. Did you intend to return at the end of each? Or did you mean for the raise to be in an else: clause?

You have designed some of these classes to take dependencies in their constructors, but you need to make sure that you are providing the dependencies when you call new.

You are missing the parentheses after UserService in this line new AppRouter(new UserService).router. It needs to be new UserService() in order to fix the syntax error. But you will still have runtime errors.

This block of code right here is a problem:

The issue could arise due to the generated npm package builds into some output folder /generated/meditation-rest-client. When being referenced by the frontend application, the api package resolves the import @angular/core to /generated/meditation-rest-client/node_modules/@angular/core, differing from the /node_modules/@angular/core in the project root.

The resolution would be to delete the /generated/meditation-rest-client/node_modules folder and the node_modules folder in the parents, except for the /node_modules. Alternatively, the generated code /generated/meditation-rest-client should be copied to some location where no parent folder contains an node_modules folder.

See https://github.com/OpenAPITools/openapi-generator/issues/8447

The problem is not mocha but axios. See this issue that causes the truncated stack trace.

This may be where the use of custom defined error response codes may come in, As long as you respect the already defined response codes. For example you could define 600 as your response code and in your API Docs specify what these custom codes mean in detail. For more information of all existing codes I would reference Iana: http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

Now if your goal is to stay within existing http response boundaries I would recommend something along the lines of:

• Unprocessable failure: Status 422
• Authorization failure: Status 403

Unable to process could mean many things such as the aforementioned business validation error.

It helps to read the whole JSON response error message from the JavaScript console or browser Network tab.

async, raw promises and done shouldn't be mixed together in tests, this results in error-prone code. Promises are often left unchained. done is often used carelessly, doesn't handle errors and results in test timeout if it's unreachable.

Since second test is a no-op and cannot timeout by itself, it's beforeEach to blame. If there's only one application instance, it's not expected to trigger serverStarted multiple times. The way how serverStarted works wasn't shown.

If the intention is to keep instances separately, it should be reinitialized for every test:

It's an asynchronous issue. You're populating the value of the array inside a callback. But because of the nature of the event loop, it's impossible that any of the callbacks will have been called by the time the console.log is executed.

You mentioned a solution involving promises, and that's probably the right tack. For example something like the following: