# About ![](https://4207139903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjbOt9KtYfZmokTYzgSHc%2Fuploads%2Fgit-blob-246073482ebafbf09bb5dd2876bf6769feeecc15%2Fbanner-8.png?alt=media) ### Qyrus Desktop Testing Service βš™οΈπŸ› οΈ **Desktop testing** is a quality assurance process that involves evaluating software applications specifically designed to run on desktop computers. This type of testing encompasses a wide range of applications, including **Windows applications**, **Electron-based apps**, and **SAP (Systems, Applications, and Products)** software. The primary goal of desktop testing is to ensure that these applications function correctly, are user-friendly, and meet the specified requirements. #### Windows Application Testing πŸ’»: * Windows applications are programs developed to run on Microsoft Windows operating systems. * Test cases may include checking user interfaces, functionality, performance, and compatibility. * Detailed reports are generated to document test results, including test case execution status, defects found, and any deviations from expected behavior. #### Electron-Based Application Testing βš›οΈ: * Electron is a framework that allows developers to create cross-platform desktop applications using web technologies (HTML, CSS, JavaScript). * Testing Electron-based apps involves validating their functionality and compatibility across multiple desktop operating systems (Windows, macOS, Linux). * Test cases may focus on Electron-specific features and functionality, as well as general application testing. * Reports provide insights into how well the Electron app performs across different platforms and browsers, identifying any issues or discrepancies. #### SAP Application Testing πŸ“ˆ: * SAP is a software suite used for enterprise resource planning (ERP) and business process management. * Testing SAP applications involves verifying that they meet business requirements, are secure, and perform efficiently. * Test cases may include business process testing, security testing, and performance testing. * Detailed reports include information on the functionality tested, any defects or vulnerabilities discovered, and performance metrics. #### Generating Detailed Reports πŸ“°πŸ“Š: * Detailed reports in desktop testing are essential for tracking progress, identifying issues, and making informed decisions. * These reports typically include: * Test case details: A list of test cases executed, including their names, descriptions, and expected outcomes. * Test execution status: Information on whether each test case passed, failed, or is pending. * Defects: A list of defects or issues found during testing, with descriptions, severity levels, and steps to reproduce. * Screenshots: Visual evidence or logs to illustrate defects or provide additional context. * Metrics: Performance metrics such as response times, resource utilization, where applicable. The detailed reports generated under each scripts of desktop testing service help stakeholders understand the quality and readiness of the desktop applications, enabling them to make informed decisions about release readiness or necessary improvements. ### Table of contents | Category | Features | | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [**Overview πŸ“–**](https://docs.qyrus.com/desktop-testing/getting-started/overview) | [QB Installation and Node Registration](https://docs.qyrus.com/desktop-testing/getting-started/qb-installation-and-node-registration/qb-installation-and-node-registration) | | **Getting Started** | | | ***ProjectπŸ“*** | 1. [Project creation](https://docs.qyrus.com/desktop-testing/getting-started/project-creation/create-project) | | | 2. [Quick Run](https://docs.qyrus.com/desktop-testing/getting-started/project-creation/quick-run) | | ***Build 🧱*** | | | **A. Test Repository πŸ§ͺ** | 1. [Creating Module](https://docs.qyrus.com/desktop-testing/getting-started/build/module-creation#creating-modules) | | | 2. [Module operations](https://docs.qyrus.com/desktop-testing/getting-started/build/module-operation) | | | 3. [Creating Script βš™](https://docs.qyrus.com/desktop-testing/getting-started/build/script-creation) | | | 4. [Script operations](https://docs.qyrus.com/desktop-testing/getting-started/build/script-operation) | | | 5. [Creating Steps and their operations](https://docs.qyrus.com/desktop-testing/getting-started/build/step-creation) | | **B. Project Setup πŸ—οΈ** | [Global Variable](https://docs.qyrus.com/desktop-testing/getting-started/build/project-setup#global-variables) | | **C. Test DataπŸ”’** | [Parameterization](https://github.com/QQyrus/Desktop-Service-User-Documentation/blob/develop/broken-reference/README.md) | | ***Run ▢️*** | 1. [Sprint](https://docs.qyrus.com/desktop-testing/getting-started/run/sprint) | | | 2. [Test Lab](https://docs.qyrus.com/desktop-testing/getting-started/run/testlab) | | ***Analyze πŸ“ˆ*** | 1. [Reports-Sprint and Test Lab](https://docs.qyrus.com/desktop-testing/getting-started/analyze/reports) | | | 2. [Mind Maps](https://docs.qyrus.com/desktop-testing/getting-started/analyze/mindmaps) | | | 3. [Tags](https://docs.qyrus.com/desktop-testing/getting-started/analyze/tags) | | ***Maintain πŸ› οΈ*** | [Shared Tests](https://docs.qyrus.com/desktop-testing/getting-started/maintain/shared-test) | | **User Actions πŸ™‹β€β™‚οΈ** | 1. [Window Actions](https://docs.qyrus.com/desktop-testing/user-actions/window-actions) | | | 2. [SAP Actions](https://docs.qyrus.com/desktop-testing/user-actions/sap-actions) | | **Advanced Features πŸ”§** | 1. [TDM and Parameterization πŸ“Š](https://docs.qyrus.com/desktop-testing/advanced-feature/tdm-and-parameterization) | | | 2. [QSpy and Recorder πŸ“Ή](https://docs.qyrus.com/desktop-testing/advanced-feature/qspy-and-recorder) | | | 3. [Import VB Script πŸ“₯](https://docs.qyrus.com/desktop-testing/advanced-feature/importing-vb-script) | | | 4. [Advanced SAP Actions](https://docs.qyrus.com/desktop-testing/advanced-feature/advanced-sap-actions) | | | 5. [Import script through XLSX and JSON](https://docs.qyrus.com/desktop-testing/advanced-feature/import-export-script) | | | 6. [Shared test](https://docs.qyrus.com/desktop-testing/advanced-feature/shared-test-component) | | **FAQ ❓** | [Common Questions](https://docs.qyrus.com/desktop-testing/faqs/faqs) | ### User Flowchart ![](https://4207139903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjbOt9KtYfZmokTYzgSHc%2Fuploads%2Fgit-blob-ed6cae6a21014508e71f009884c586d2af2672fc%2Fds-flowchart-8.png?alt=media) --- # 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/desktop-testing/readme.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.