> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/testy/testowanie-integracji-z-uslugami-zewnetrznymi.md). # Testing integration with external services Integration tests are very important, because **the application communicates with many external systems** e.g. CRM or payment systems. If the integration does not work properly, it results in business errors, data loss, or incorrect operation of the entire process. ## Integration testing methods ### Mocks * are simulations of responses from external systems, * the ability to test various response scenarios, * tests can be independent of service availability. ### Input data tests * validation of the correctness of sent requests (e.g. JSON, XML structure). ### Output data tests * checking whether the system correctly processes data returned from the outside, * handling errors and exceptions. ### Unit tests in scripts Learn more: [Script unit tests](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/testy-jednostkowe-skryptow.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/testy/testowanie-integracji-z-uslugami-zewnetrznymi.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.