# Sprint Reports Users have the capability to execute the ***Test Scripts*** in the Sprints and subsequently access the results within the ***Reports*** section located under the ***Analyze*** category. It is noteworthy that there are ***two*** distinct ways through which users can review these reports. 1. Upon entering the project, focus your attention towards **Analyze** category then look for the **Sprints** section, Following of the Sprints you will encounter a clickable button designated as **Reports** which users can select to view the reports of Test Scripts. ![Sprints\_Analyze](/files/LPr7Qx7hR39i1yf2otG1) 2. Upon entering the project, focus your attention towards top upper-left corner of the screen and click on the icon resembling a ***Hamburger*** menu. Beneath the header labeled ***Reports***, you will find an option titled ***Active Sprint Report*** which users can select to view the reports of Test Scripts. ![Active\_Sprint\_Report](/files/4DJvUYVEnBVviX81ex4B) Upon clicking the Reports button in Analyze Category or Clicking the Active Report button from Hamburger menu user will be navigated to Sprint Reports Page. On Sprints Reports Page user has the option to view the results which is executed with ***Active Sprints*** and ***Previous Sprints***. Under Active Sprints user has the options for : 1. [Sprint Dashboard](#SprintDashboard) 2. [Sprint Details](#SprintDetails) 3. [Dry Runs](#DryRuns) 4. [Executions](#Executions) 5. [Performance](#Performance) #### Sprint Dashboard Here users have the capability to ascertain the comprehensive count of ***Total*** executed Test Scripts within the Sprints, including a breakdown that delineates the number of Test Scripts that have been successfully ***Passed*** and those that have encountered ***Failure*** and on the ***Browser*** in which Test Script is executed. * We can also get the details on ***Total Number of Test Suites***, ***Total Number of Test Scripts*** exists within Sprints. * Also user get the details on ***Sprint Start Time***, ***Sprint End Time*** with the number of ***Days remaining*** for the completion of Sprints. * On the top upper-right corner of the screen we can see the ***Total Number of Active Runs Count***. ![Sprints\_Dashboard](/files/6WWQX9tN1HR42dV72qsz) * Users are also provided with detailed information concerning the count of daily executed runs in the graphical representation. * Users are provided with information on Most Executed Test Scripts with their Pass Percentage. ![Sprints\_graphs](/files/GLEUqcGCW9nVTopJ5QQp) #### Sprint Details * On the left-hand side of the screen, there exists the option to make a selection of the specific sprint for which we wish to access and review the results. * Within the Sprint details, users have the capability to access Execution reports for the Test Suites, encompassing detailed information about the contained Test Scripts. Additionally, users can retrieve the overall Pass Percentage for the executed Test Scripts, providing a holistic view of the test script success rate, which contain 1. ***Test Suite/ Test Script Name*** - Name of the executed Test Suite/Test Script. 2. ***Total Executions*** - The number of times the Test Script has been executed. 3. ***Total Pass*** - Total number of Test Scripts that has been Passed. 4. ***Total Fail*** - Total number of Test Scripts that has been Failed. 5. ***Last 5 Executions*** - Results of last 5 Executions. 6. ***Pass %*** - Over all Pass % of the Test Suite. * On the top right side we can get the information on number of total ***Active Runs***. ![Sprint\_details](/files/zS0b2QKmrWnEuaBtTU3o) * By clicking on the arrow button located at the end of the test suite, users can retrieve the precise count of all Test Scripts contained within that particular Suite. * By clicking on the arrow button located at the end of the Test Script, users user can get the detailed information on executed Test Script which contains ***Executed Date***, ***Execution Time***, ***Platform***, ***Browser***, ***Status***, and ***Version of the Browser***. ![Sprints\_details](/files/urFQXllPZsidjYM6Erh3) #### Dry Runs Within Dry Runs, users have the capability to access execution reports for Test Scripts and Test Suites, encompassing detailed information about the Test Scripts, which contains 1. ***Test scripts*** - Test Script Name. 2. ***Executed On*** - The specific date of execution for the Test Script is indicated. 3. ***Execution Time*** -The duration of time required to execute the Test Script. 4. ***Platform*** - Operating System in which Test Script has been executed is specified. 5. ***Browser*** - The browser in which the Test Script has been executed is specified. 6. ***Status*** - It provides the status of the individual Test Script. * We have a ***Search*** functionality available for the purpose of quick find of a Run executed. * Users are provided the ***Select Sprint*** option to select the Sprint on which particular Sprint he need to get the details. * On the top upper-right corner of the screen we can see the ***Total Number of Active Runs*** count. * Within the Test Script report Page, users have the capability to view a ***Video*** recording of the executed Test Script, accompanied by details regarding the executed ***User*** . * Users are provided with the option of a **Refresh** button. Upon selecting this button, users can get to know the accurate status of the run. ![Dryruns\_Sprints](/files/4pqdF9YHQM769Pd60b3N) Users can access additional options by clicking on the ellipsis icon represented by three dots on the report, which contains * ***Download Report*** - Upon selecting this button, users can download the corresponding Test Script's and Test Suite report. * ***Mail Report*** - Upon selecting this button, users can Mail the corresponding Test Script's and Test Suite report. * ***Retry*** - Upon choosing this button, users can initiate the re-execution of the Test Script, resulting in the creation of a distinct record for the Test Script and Test Suite. * ***Delete*** - Upon choosing this button, users can delete the report of the Test Script and Test Suite. ![dryrun\_options](/files/hwOVj0UzCRuf2gjAejhW) Upon clicking the right-facing arrow button on the side of the Test Script Report, users will be directed to a details section i.e, is **Test Report**. Here, they can access a entire view of the report, enabling them to review the individual steps within the Test Script, distinguishing those that have ***Passed*** from those that have ***Failed*** with the ***Screenshot*** of that step. For [Detailed Execution Report for Test Scripts and Test Suites](#detailedreport) can refer this #### Executions Within Executions, users have the capability to access execution reports for Test Scripts, encompassing detailed information about the Test Scripts, which contains 1. ***Test scripts*** - Test Script Name. 2. ***Executed On*** - The specific date of execution for the Test Script is indicated. 3. ***Execution Time*** -The duration of time required to execute the Test Script. 4. ***Platform*** - Operating System in which Test Script has been executed is specified. 5. ***Browser*** - The browser in which the Test Script has been executed is specified. 6. ***Status*** - It provides the status of the individual Test Script. We have an option of selecting of particular Sprint to get the details of that Test Scripts. * We have a ***Search*** functionality available for the purpose of quick find of a Run executed. * Users are provided with the option of a **Refresh** button. Upon selecting this button, users can get to know the accurate status of the run. * Within the Test Script report Page, users have the capability to view a ***Video*** recording of the executed Test Script, accompanied with details of the executed ***User*** and the associated overseeing entity, known as the ***Healer***. ![Sprint\_Executions](/files/0C7xpbfMa6QU1j7QH7W2) Users can access additional options by clicking on the ellipsis icon represented by three dots on the report, which contains * ***Download Report*** - Upon selecting this button, users can download the corresponding Test Script's and Test Suite report. * ***Mail Report*** - Upon selecting this button, users can Mail the corresponding Test Script's and Test Suite report. * ***Retry*** - Upon choosing this button, users can initiate the re-execution of the Test Script, resulting in the creation of a distinct record for the Test Script and Test Suite. * ***Delete*** - Upon choosing this button, users can delete the report of the Test Script and Test Suite. ![Sprints](/files/rNLNk76yzhJBWo9WF1nx) **Detailed Execution Report for Test Scripts and Test Suites:** Upon clicking the right-facing arrow button on the side of the Test Script Report, users will be directed to a details section i.e, is **Test Report**. Here, they can access a entire view of the report, enabling them to review the individual steps within the Test Script, distinguishing those that have ***Passed*** from those that have ***Failed*** with the ***Screenshot*** of that step. * On top right side of the screen users are provided with information on total Test Cases , total Passed Tests, total Failed Tests. * Also get the detailed information in which Test Script is executed ***OS***, ***Browser***, ***Browser Version***, ***Environment*** with ***Resolution***. * And information on ***Executed Date***, ***Start Time***, ***End Time*** and ***Execution Time*** of the executed Test Script. * Details of individual steps contains : **Test Script Name, Step Description, Expected output, Actual Output, Data and Status of the Report** with ***Test Case Execution Time***. ![Sprint\_TestReport](/files/v9hSDbyS8Vd28g8AQGEZ) When we click on Test Suite report we can view the details of which script executed in the Test Suite with there steps and the time taken to execute each Test Script with there Status with Screenshot. ![TestSuite](/files/WDrtdzcs72SD9I1LVJzG) On this particular page, users are afforded a range of functionalities such as, * ***Video*** - Users can avail the Video recording of the executed Test Script and Test Suite. * ***Email*** - Users can transmit the results of the executed Test script and Test Suite via Email by entering the respective mail id's. * ***Download*** - Users can download the comprehensive report of the Test Script and Test Suite which will be downloaded as PDF for analyzing their results. * ***Performance Metrics*** - Users can preview the associated Performance Metrics for the Test Script and Test Suite. * ***Report*** - Users can have a quick view of the Report which will be opened in a seperate tab by clicking on the respective icons . ![sprint\_options](/files/E6lcdoWojq2YtEvZLDHD) On clicking the ***Console Logs*** button user can get the details of the Logs for the executed Test Script. ![consolelogs](/files/Ql6hkGTQkbFZcnT8VJNr) #### Performance Within the Performance user can get the details of the Performance Runs which contains 1. ***Test Scripts*** - The Name of the Test script. 2. ***Total Simulations*** - The number of times Test Script got executed. 3. ***Start Time*** - It is the time where execution begins. 4. ***End Time*** - It time where execution got completed. 5. ***Executed By*** - The user who has executed the Test Script. 6. ***Status*** - It provides the status of the Test Script. * Users are provided with the option of a **Refresh** button. Upon selecting this button, users can get to know the accurate status of the run. * On the right side of the Test Script Report user is provided with ***Deletion*** icon to delete the script report. ![Performance](/files/ziNa9fPHEWXazQ5qqxnz) Beside the deletion icon user is presented with a arrow button clicking on which user get the details of the executed Test Script which contains ***Number***, ***Executed On***, ***Execution Time*** and ***Status*** of the Test Script. ![Sprints\_performance](/files/eO0tLk4rUNsJmMmilQTo) By clicking on the ***Previous Sprints*** tab user will be directed to previous sprints page, where user gets the details of previously completed Sprint with the Date. ![previous\_sprints](/files/vs1RVkBsjKdeDFvs3lnN) --- # 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://docs.qyrus.com/web-testing/analyze/sprints.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.