Simulate third-party services in application-go + BDD-java

What php editor Zimo will introduce to you today is the method of simulating third-party services in application-go BDD-java. During software development, we often need to interact with third-party services, but during the testing phase, we may not have direct access to these services. To solve this problem, we can use application-go and BDD-java to simulate the behavior of third-party services for more effective testing. Next, let us take a look at the specific implementation method!

Question content

I recently started researching BDD (using Gherkin Restassured). Need to simulate third-party serviced, the following is my use case.

1. Service A internally calls service B
2. The application is located in goLang.
3. BDD uses Java language.

We have a CI pipeline running that generates the rpm and deploys the rpm into the virtual machine. On this VM we run BDD (Currently Service-A and Service-B are deployed on the same VM)

Is there a way to mock Service-B so that I don't have to rely on Service-B? If yes, what is the best approach here.

Tried goLang httptest to mock the service at the unit test level. But how to simulate after creating rpm in pipeline using BDD.

Thank you

Workaround

If your service A calls service B internally, rather than via Web or RPC, then you can use dependency injection to inject service B's "false" "Version. (Note that this does not necessarily involve dependency injection frameworks; constructor-based and property-based injection are also valid). If service B has no interface, extract one and use a thin adapter to call the real service or fake service depending on the environment.

As long as the scene only interacts with Service A's UI or API, you don't need to change the scene.

You will need to change the way your build pipeline works so that it uses your fake code for deployment instead of your real code.

You can even do this at runtime, switching from the fake to the real thing by having the adapter call the relevant service. Switching or deployment can be triggered by environment variables or build parameters.

But please be careful not to deploy test services to production!

If you use continuous deployment, then ideally the last step in the build pipeline should deploy and test interaction with the actual service. If for some reason this is the only way you work, there are still a few things you can do that might help:

• You can stub the data used by service B so that it behaves in a predictable manner

• You can use test instances. Please contact your service provider to see if they have services that may work for you. I would suggest that you should still check if the deployment of the actual service was successful, preferably using some kind of automated testing, even if it has to be run in production. Just do a basic smoke test to check if your system is connected. Note that the easier it is to deploy, the easier it is to recover from errors; if you can't deploy quickly, then you'll need more thorough inspections.

If the RPM was created and deployed without any kind of fake or test instance, and you cannot configure the environment to use such a fake or test instance, then you will not be able to mock it. The build pipeline must be part of the deployment forgery. If you have control over the CI pipeline, this won't be an issue; otherwise, contact your build team. They may have experience or be able to refer you to others who can help you. After all, great BDD is driven by dialogue!

The above is the detailed content of Simulate third-party services in application-go + BDD-java. For more information, please follow other related articles on the PHP Chinese website!