> 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/struktura-aplikacji-low-code-i-metodyka-testowania.md). # Low-code application structure and testing methodology ## **Application structure and tests** The Eximee application is a container for artifacts ([Business application](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa.md)). ### **Form tests - what is worth checking?** * the correctness of the fields (whether they are visible, required), * validations and business rules, * integration with the data model (whether data is correctly fetched and saved), * the appearance of the content and the layout of the fields. More about forms: [Forms](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze.md). ### **Data model tests - what is worth checking?** * whether all fields required in the application are present, * whether default values are set according to the requirements, * whether changes in the model do not cause errors in forms or processes using this model. More about the data model: [Data model](/documentation/documentation-en/budowanie-aplikacji/model-danych.md). ### **BPMN process tests - what is worth checking?** * whether the process flow is consistent with business requirements (paths, conditions, decisions), * whether integration with forms and the data model works correctly, * whether script task calls and exception handling are correct. More about processes: [Business process](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy.md). ## **Integration and end-to-end tests** ### **Scope of integration tests** * connection of the form with process logic (BPMN), * verification of ScriptCode and business rules, * integrations with external systems (CRM, payments), * generating PDF documents and passing them further in the process. * omnichannel support – transferring context between channels (desktop → mobile). ### **Scope of end-to-end (E2E) tests** * full flow form → process → document → integration → final status, * checking whether business logic, interfaces, and integrations create a coherent experience. * testing critical and business scenarios in line with the requirements. --- # 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/struktura-aplikacji-low-code-i-metodyka-testowania.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.