Questions about connecting algoQA with your CI/CD, ALM, and defect tracking tools. Select a question to expand its answer. To integrate API validation with database verification in algoQA, follow these steps: 1. Perform API automation using the algoQA API Collection. 2. After successful API validation, perform database verification by adding a parameter in the node configuration. 3. Create a new node for database verification in the Canvas. 4. In the Node, click the Edit Icon to open the Control Panel List Window. 5. Add the required parameter in the Control Value text box. For example, if you add a UI element as DB Query, enter the parameter value as `PostgreSql_#Query1:-`. Replace `` with your actual query statement. The platform provides built-in actions for both API and database interactions, which can be seamlessly integrated with UI-based test scenarios. DB support includes commonly used databases such as MySQL and PostgreSQL. Integration with Azure/ADX databases can be achieved through custom actions. Yes, scripts generated by algoQA are readily executable in CI/CD pipeline. For example, you can leverage CI/CD environments, such as Jenkins for nightly executions. Jenkins, Azure, Bamboo, and GitLab. When scripts are generated in algoQA, they are not automatically executed within a CI/CD environment. By default, to integrate algoQA into a CI/CD pipeline, you need to use specific execution commands to run these scripts as part of the CI/CD process. You can import test cases from TestRail into algoQA. Here is how: - Export test cases from TestRail in a format that algoQA supports, such as CSV. - algoQA can also upload the test results from generated scripts to TestRail. Export Test Cases from TestRail: 1. Log in to your TestRail account. 2. Navigate to the project containing the test cases you want to import. 3. Go to the "Test Cases" tab and select the test cases you want to export. 4. Click on the "Export" button and choose the desired export format (XML or CSV). 5. Save the exported file to your local machine. 6. Use prompt engineering or auto test case generation feature within algoQA to generate test cases which are the same as the TestRail test cases. To execute test cases directly in algoQA without using TestRail, follow these steps: 1. Record or edit your test scenarios using the Test Design feature. 2. Tag each test case with unique identifiers or labels using custom tags. 3. Ensure all dependencies, such as browser drivers, libraries, and other necessary tools, are correctly installed and configured. 4. Set environment variables correctly to access the required resources. 5. Execute test cases in batches using one of the following methods: - Command Prompt Execution: Navigate to the directory where the scripts are saved and use the appropriate command to run them. - Jenkins Integration: Integrate with Jenkins to schedule and manage the execution of scripts as part of your CI/CD pipeline. - Third-Party Cloud: Execute the scripts in a third-party cloud environment, such as LambdaTest. Yes, algoQA supports direct import of Postman collections and Swagger collection, with WSDL support, enabling teams to reuse existing assets immediately without rework. Importing a Swagger or Postman Collection: 1. Create a Project: - Name your project (e.g., "API Automation using algoQA collection"). - Select "API Automation." - Click "Create" to initiate the project setup. 2. Upload an API Collection: - Click on the upload icon to import your Swagger or Postman collection. Postman: - Manual or semi-automated - Script-heavy for automation - Limited at scale - Not suitable for enterprise regression automation - High maintenance cost as APIs evolve algoQA: - Scenario-Based Automation: algoQA offers scenario-based API automation, allowing users to chain multiple API requests and integrate UI and API testing. - Script Generation: algoQA can generate test scripts in multiple programming languages and frameworks. - Reports: algoQA provides auto-generated HTML reports that verify API responses and corresponding status codes. - UI and API Integration: algoQA captures UI workflows and allows logging of API calls from UI interactions, enabling intertwined UI and API testing. In summary, while both tools allow API request creation and execution, algoQA provides more comprehensive automation features and script generation capabilities compared to Postman. Yes, algoQA supports SOAP API automation. Yes, algoQA supports chaining steps that involve hitting an API to set data, performing actions on a web application, and validating data in a database. Yes, algoQA supports all these databases. algoQA's Copilot is an internal AI assistant within the platform, not linked with Microsoft Copilot. It assists users in creating, executing, and analyzing test cases within algoQA. The solution supports fully on-prem or hybrid cloud deployment, integrating enterprise LLMs (Azure, spectrum GPT), keeping all automation data and models within the customer's secure perimeter. Yes, algoQA supports scheduled and overnight test execution, report generation, and ensures tests run without manual intervention for 24/7 coverage. Yes, algoQA identifies test gaps and suggests new scenarios by checking developer code throughout the CI/CD process, ensuring scientific coverage and continuous improvement. algoQA offers scenario-based API automation similar to Postman but integrates UI and API, allows scenario chaining and script generation in multiple languages, and can save/download logs and results for CI integration. algoQA mostly captures UI workflows. API calls from UI can be logged via network browser tools, and API validations can be integrated as additional checks. Both UI and API can be tested and intertwined for scenario-based automation. You can modify the following details of an individual API request within an API collection: - Endpoint URLs: Update the URL for the API endpoint. - HTTP Methods: Change the HTTP method by selecting the appropriate option from the drop-down list (GET, POST, PUT, DELETE, PATCH, and OPTIONS). - Headers: Edit or add HTTP headers. - Parameters: Modify query parameters or path variables. - Body: Change the request body (for POST/PUT requests), including data formats like JSON, form-data, or raw text. - Authorization: Update authorization settings, such as tokens or API keys. In Postman, Pre-request scripts functionality is used to run custom scripts before API requests are sent. They run in the context of the request, allowing you to modify request parameters, headers, or body content dynamically. The same functionality can be used in the algoQA API collection by writing custom methods. For example, API token authentication and configuring environmental variables. algoQA generates test cases using API collections, which can be in Swagger/Postman collection or in Excel format. The API collection is uploaded to algoQA, and the platform generates the test cases and scripts. Even if the Swagger files are not well-documented or complete, if you have proper working APIs, you can use algoQA to generate test cases and scripts.

Integrations & CI/CD