# Idea

<img src="https://1911987200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN272nVe7mr4ClIEh2f89%2Fuploads%2F7VzUUXPKJb9NzkYOju4H%2Ffile.excalidraw.svg?alt=media&#x26;token=96e3d2a6-d78d-4db8-894e-db136ba9d51f" alt="Overview" class="gitbook-drawing">

The idea is that while your framework runs, we would spawn Handshake Server through their listener, The Server Job is simple, it just needs to store the results in the right tables.&#x20;

Once Tests are completed, we will run a command to transform the results, we calculate certain outputs for example:

* Calculate the Broken Suites based on the Assertions Added through their status
* Link Suites with a previously retried suite
* Status of the Test Run
* Number of Indirect Test cases for a suite
* Generate the JSON for all the stored tables to generate the reports.

Once done, we would move the dashboard build to the desired location and the generated JSON to the static build. once done we can host the folder.

In the rest of the pages, we can rest on how each of these steps is done through modules.


---

# 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://rahuls-organization-17.gitbook.io/handshake/architecture-and-contribution/architecture/idea.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.
