# Smoke Testing When the build is ready for QA then, we will take up the release build version code and start testing the major features of the application to ensure that all the functionality is working as expected or not by following the phases * One-step Installation - Positive Scenarios to be executed * API karate Framework - Calling Spec , dimension , Ingestion, and Schedule APIs for each program wise to verify able to add schemas to db , input files to buckets, and verify the ability to schedule the Nifi processor and validate the processing of the ingested input files * Verify the after Nifi Processing of the files whether datasets of all the programs have been created tables or not in the database * Verifying the Visualization * Login Page * Dashboard - Summary Statistics * All Program Dashboard - Data is showing up or not, and each web feature functionality is working as expected or not --- # 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://cqube.sunbird.org/qa-testing/functional-testing/smoke-testing.md?ask= ``` 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.