> For the complete documentation index, see [llms.txt](https://moataz-salahs-organization.gitbook.io/chatter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moataz-salahs-organization.gitbook.io/chatter/testing-and-debugging/conducted-tests.md).

# Conducted tests

<mark style="color:blue;">**Unit and Feature Testing**</mark>

To ensure the reliability of Chatter, we use a combination of unit and feature tests:

**Unit Tests:** We test critical functionalities such as login, registration, and profile management to verify that each component works as expected.

**Feature Tests:** Comprehensive feature tests cover user flows and interactions, ensuring that all parts of the application function correctly.

<mark style="color:blue;">**Manual Testing for Real-Time Functionality**</mark>

Real-time features, such as chat updates and notifications, require manual testing to validate their performance under various conditions. We simulate different scenarios to ensure that messages are delivered and received in real-time, and that notifications are displayed correctly.

<mark style="color:blue;">**End-to-End Testing**</mark>

Our end-to-end tests encompass the entire application:

**Comprehensive Testing:** We test complete user workflows, from initial registration to using the chat and updating profiles. This approach ensures that all features work together seamlessly.

**System Testing:** We validate the integration of all components, including real-time messaging, notifications, and user interactions, to ensure a smooth and reliable user experience.

<mark style="color:blue;">**Debugging Real-Time Issues**</mark>

For debugging real-time issues:

**Monitor Pusher Console:** Use the Pusher console to check for any issues with event broadcasting and connectivity.

**Check Laravel Logs:** Review Laravel logs for errors and warnings related to broadcasting and real-time functionality.


---

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

```
GET https://moataz-salahs-organization.gitbook.io/chatter/testing-and-debugging/conducted-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.