> For the complete documentation index, see [llms.txt](https://dev.cubrid.org/dev-process/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.cubrid.org/dev-process/dp-en/workflow-after-code-merging-1/qa-report.md).
# Checking the QA Report
The QA team uses a CI tool called Jenkins to run the test system. When the Pull Request is merged, Jenkins is connected to Github and automatically tests the merged commit. (Reference: )
All tests are performed in Jenkins, and the result report is available at . On the left side of the page, you can see the test result report by version and a summary of the latest test report is displayed on the right side.
If you click the test result report on the left, there is a tab as shown in the figure below. Each shows the results of testing for function, performance, and memory leaks. (The button on the first right 'verify status' is not used by the development team).
{% hint style="info" %}
Meanwhile, QA test reports are sent periodically by email if you register in the developer mailing lists.
Make sure to check for functional tests, performance tests, and memory leaks when merging. In particular, if the performance test degrades by more than 5%, it is necessary to see if there is a problem.
{% endhint %}
The test is divided into a functional test and a non-function test. In terms of the functional tests, we are conducting tests for Linux and Windows environments respectively. Windows currently test fewer items than Linux.
---
# 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://dev.cubrid.org/dev-process/dp-en/workflow-after-code-merging-1/qa-report.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.