> For the complete documentation index, see [llms.txt](https://cqube.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cqube.sunbird.org/qa-testing/functional-testing/system-testing.md).

# System Testing

This can be done when there is no blocker and major defects are on the defect list. Then it would be the final round of testing activity before moving to production/sign-off from Quality Assurance of the Application&#x20;

* One-Step Installation - AWS , SDC/On-premise , Oracle&#x20;
* API Testing - Spec , Ingestion , Dimension , Scheduler&#x20;
* Nifi Processing Validation of ingested program files&#x20;
* Database validation - verification of all the programs datasets are created or not&#x20;
* Visualization Testing - Login Page , Dashboard Page , Program Dashboards and their each tab functionalities to be tested&#x20;
* Verification of Logout , Release date , Release version and Resolutions tests


---

# 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://cqube.sunbird.org/qa-testing/functional-testing/system-testing.md?ask=<question>&goal=<endgoal>
```

`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.
