# Organize tests

Testing is a lot different from coding and often developers tends to be stuck on what to do on their first tests.

This totally normal and natural and this part will be focusing on how and what to write in a test to make it effective.

The first point to get is what a test can and cannot do. When testing software it is possible to assert for the presence of a specific behavior, but it is impossible to assert that bugs will be totally absent within the software.

In other term it is possible to assert that a bug is not present but impossible to insure the software is bug free.

With that in mind it is easier to understand what will be done within the test. Setting the software in a certain context that needs to be tested. Then run the logic to test. Finally, assert that the new behavior is the one expected.

To make sure theses 3 steps are actually done a really common pattern while writing tests is the AAA.

* **Arrange** : this part is focused on setting the initial state from the application to make conform to the state we want to test.
* **Act** : during that part we need to execute the application.
* **Assert** : at that moment we are making sure the output state is the one we expected.

{% @mermaid/diagram content="    flowchart TD
Arrange\[Setup the software]
Act\[Execute the logic to test]
Assert\[Make sure the state is the one expected]
Arrange --> Act
Act --> Assert" %}

A good practice while developing is to use the Command Query Responsibility Segregation. When combined with testing it becomes even more powerful as it is possible to reuse commands and queries already implemented within the tests and actually make integration tests easier.

As when arranging the state it is about changing the state from the software commands can be used at that level. In a same fashion query can be used to make sure it is possible to fetch the data to assert without modifying the state making it safer.

{% @mermaid/diagram content="    flowchart TD
Arrange\[Run commands to setup the state]
Act\[Execute the logic to test]
Assert\[Assert results from queries]
Arrange --> Act
Act --> Assert" %}


---

# Agent Instructions: 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:

```
GET https://wp-launchpad.gitbook.io/launchpad/tutorials/notions/index/organizing_tests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.