I am creating true applications that synchronize data between different systems, services and APIs.
My reconfiguration application is as follows:
- Selecting an HTTP endpoint to get some user information
- User service to User ID Enrich the message
For example, I am testing the data changes which I consider to test the unit. I am testing that if the user (stubbed) response has been returned from the user service then the value is properly rich by using my expression. I think it will be a functional test?
But should I test the polling? Is each ending point called? Will this be the integration test?
What works for me is to ensure that I define "units" My software is in a way that allows me to talk about just about my application, and allow facets to change which I need a reunion. Virtually in ESB applications, it sometimes leaves me with a lot of unit tests that look like those I'll write in a Java program. Most of my unit tests come out from functional tests, and the number of in-process testing for the actual system required to integrate me includes a few numbers.
I have tried to use Munit to complete it, but some design decisions that make this style of testing difficult, so my unit test usually comes from the functional testcases.
For your application, I can test as the following:
- Make sure that the HTTP endpoint is correctly voted up
- A unique ID has been returned from the user service, to ensure that the targeted service is called the correct message
- If the change logic is complex, then I can add many tests which can be used in different edges Be sure to find out My conversion is working properly
- Sometimes the web services require some headers or authorization tokens, so I often prepare several tests to ensure that they are < Note that I do not explicitly tell that my message gets "rich" or "change" mid flow, because these steps are only a means to end Change the steps The road should be set for the road or using XSLT instead of Java, these tests will not need to be replaced.
To make an in-process test pair for your HTTP services, take a look.
No comments:
Post a Comment