ts-redux-react-realworld-example-app VS Pact JVM

Maybe you need to tweak the tsconfig.json? I've tested tsserver in this codebase and it worked fine (for my standards). Here is the config I used.

We will use ts-redux-react-realworld-example-app project which implements the front-end in TS for realword app using React/Redux.

In this example I wanted to find out: "what happens if I click the publish button when creating a new article?" inside the React RealWorld App (GitHub) If this process brings up new questions, I write them down and try to answer them in a collapsible text block. Sometimes I decide to postpone answering a question. Then I mark this question with a "🤔" emoji, so I don't forget that I haven't answered it yet. In this example I asked myself the question: "Why do we set state.submitting flag to true . Which part of the app code reacts to this state? " I assumed this flag could trigger something relevant in the code, but it turned out it only disables the editor form.

probably you can take a look on an example like this : https://github.com/angelguzmaning/ts-redux-react-realworld-example-app

API Contract Testing might be worth exploring. Gives you the ability to run it quickly locally or in CI/CD. A centralized way to validate if your changes broke another service might also be interesting. That series of videos from the same team is gold: https://docs.pact.io

We use Pact for contract testing https://docs.pact.io/

The introduction here is quite good: https://docs.pact.io/

Pact.Net documentation: https://docs.pact.io/ Mountebank documentation: http://www.mbtest.org/ The Microsoft.AspNetCore.TestHost package on GitHub: https://github.com/aspnet/AspNetCore/tree/main/src/Testing/Microsoft.AspNetCore.TestHost

There's also https://docs.pact.io/ but I haven't had time yet to really look into it but probably someone else can tell something about it.

This PoC shows a step by step implementation of contract testing using Pact.

Contract tests assert that inter-application messages conform to a shared understanding documented in a contract. Without contract testing, the only way to ensure that applications will work correctly together is by using expensive and brittle integration tests.

If you are updating your API based on user feedback, you can work with your team or stakeholders to build an API contract describing how your API should function. You can use JSON schemas to document your API’s endpoint response codes and set up the contract. The contract must be accepted by all parties. Then, any changes made to the API must pass the contract test before being approved. Contract testing can be automated and incorporated into your CI/CD pipeline. Contract testing tools include Pact and Spring Cloud Contract.

Pact.

I have contract tests (https://docs.pact.io/) to ensure the integration works.