> 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/walidacja-formularzy-i-logiki-biznesowej.md).

# Form and business logic validation – manual and exploratory tests

Forms are **a key point of contact between the user and the application**. Errors in validation or business logic can lead to incorrect data, user frustration, and even legal risk.

### Black-box techniques

* partitioning into equivalence classes (equivalence classes - sets of input and output data for which we assume the system will behave in the same way).
* boundary value analysis,
* decision table-based testing,
* state transition testing.

### Manual testing

* systematic checking of fields and rules according to a checklist,
* we check, among other things, the correctness of fields, error messages, and the correctness of the flow.

### Exploratory testing

* a less formal approach – the tester takes on the role of the user,
* looking for unusual scenarios, e.g. very long field values, unusual data formats (e.g. dates), omission of required fields
* goal: to discover errors that were not anticipated in the analyses.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/testy/walidacja-formularzy-i-logiki-biznesowej.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.