Questions about designing tests, generating test cases, and handling test data. Select a question to expand its answer. You can create multiple Feature Files in the following cases: - Individual test case in a Feature File. - Test cases related to one module in one Feature File. - Different modules in different Feature Files. You must modify the Test Design for the changes in the application and generate test cases to reflect changes. You can selectively generate the test case and test scripts for the given change. Verification steps can be added to any scenario by including a verification action after the action that requires validation and before the next action in the scenario. For example, to verify the text displayed on a button after it is clicked, add the "Verify Text" action. For detailed guidance, see the [Validating Element Visibility with verify text Action](/build-and-automate/using-algoqa-actions/default-actions/validating-element-visibility-with-verify-text-action) article. algoQA generates combinatorial datasets by both adhering to and intentionally violating defined business rules, covering invalid, incorrect, boundary, illegal, and edge-case values. It works by taking defined input parameters, their possible values, and any constraints, and then producing a minimal set of test cases that still ensure coverage of all required combinations. This helps significantly reduce the number of tests while maintaining high defect detection effectiveness. algoQA leverages AI-driven prompting to produce optimal test cases. The more well-defined and detailed the input prompt, the more accurate the output. The combinatorial datasets help with coverage and AI helps with relevance. To generate test cases with only the home page or partial functionality, you need to ensure that the feature and UI elements related to the partial functionality are selected before clicking the "Generate" button. If the required elements are not selected, the test case generation might fail. For home page testing, make sure the home page is the starting point for the scenario you want to generate test cases for. If the scenario involves partial functionality, ensure that all related elements are included in the selection. After recording a scenario in algoQA, you will see a 'Scenario created successfully' message in the Recorded Scenarios window. This indicates that the scenario has been saved. Yes, algoQA supports test case deduplication. To identify and remove duplicate test cases, navigate to the Test Cases, select the 'De-duplicate' option from the more menu (3 dots), and follow the steps provided in the 'Deduplicate TestCases' pop-up window. The platform generates a report detailing the identified duplicates and the revised list of unique test cases. The algoQA platform's Feature File quality report validates the syntax and structure of the Gherkin-based Feature Files. It checks for proper usage of keywords, correct indentation, and the presence of required elements such as Feature, Scenario, Given, When, Then, and Examples. It does not validate the functionality or behavior described in the Feature Files. Yes, product owners and non-technical users can contribute to test scenario creation in algoQA. The platform is designed to be intuitive and easy to use, allowing anyone to modify test designs and generate test cases for changes in the application. However, if users require more advanced customization, automation engineers and developers can write custom methods for incorporating application-specific logic. Product owners can contribute to test scenario creation in algoQA by using the Test Design workflow. They can view, add, search, and filter scenarios in the Scenario List screen. Product owners do not need technical knowledge to use this feature, as it is domain-intuitive and easy to use. If multiple users work on the same scenario, the active user must save their changes before another user can edit it. In a centralized project, an admin can also uncheck scenarios being worked on by another user and generate test cases. algoQA does not use Record and Play functionality to record test scenarios. Instead, you can begin the process of automation using algoQA even without writing any code for the application under test. You can start with the same inputs as the development streams, such as Wireframes and Swagger documents. To create a test scenario, you can use the Record Scenario feature or edit it in the Edit Scenario Form and add custom tags for organization. algoQA helps identify missing test scenarios through its requirement tracking and traceability features. By ensuring that all requirements are covered by test cases, it assists in identifying any missing test scenarios. Additionally, it can help identify impacted test cases for a given code change, making it easier to identify and address any new test scenarios that may be required. Yes, when discussing test design in the context of algoQA, the term refers to both the creation of feature files and the subsequent generation of executable test scripts. Feature files serve as the input for test automation, and they are transformed into test scripts by the platform. This process allows testers to design and execute tests based on the requirements, ensuring that the expected behavior of the application is thoroughly tested. algoQA supports various test design approaches including prompting, online recording, offline recording, feature file to scripts conversion, and requirements to test cases and scripts generation. You have to input the expected data in algoQA, and algoQA can generate the combinatorial data sets based on business rules provided by the user. algoQA generates test data into a separate TestData yml file. Environment-specific data is managed in the yml files. Yes, test data can be decoupled from scripts in algoQA using the Data Decoupling option. This allows for data-driven testing and the use of separate YAML files for different environments or scripts. To use this feature, navigate to the Project Settings page, select the Data Decoupling option, and click Submit to generate a separate YAML file. Alternatively, you can use the Data Set option or upload an existing data set to generate test data in a separate YAML file. Yes, the algoQA tool validates the UI table data with XML, CSV, Excel, PDF, and other custom files. In Test-Driven Development (TDD), the quality of test cases is determined by several factors: 1. Completeness: Test cases should cover all possible scenarios, including edge cases and negative tests. 2. Independence: Each test case should be independent of other test cases, meaning that the outcome of one test case should not affect the outcome of another. 3. Maintainability: Test cases should be easy to understand, modify, and maintain as the codebase evolves. 4. Reliability: Test cases should consistently produce the same results, ensuring the stability and accuracy of the test suite. 5. Readability: Test cases should be well-written and easy to read, making it clear what is being tested and the expected outcome. In the context of algoQA, you can create and manage test cases using the platform's features, such as the 'Follow Me' feature and the 'Auto test case generation' capability. These test cases can be designed based on project requirements and then transformed into test scripts using profiling and other features. By focusing on the quality of your test cases, you can ensure effective testing and maintain a robust test suite in your workflow. algoQA supports end-to-end testing and can handle UI, API, and database interactions within a single test case. You can generate Negative scenarios by generating combinatorial datasets using an appropriate feature. algoQA allows writing negative tests using possible variants of valid and invalid data inputs. This approach creates stable and reliable negative tests for applications. You can mention specified values that lead to exceptions and assign corresponding error messages. It will also help you identify errors and take corrective measures. algoQA offers two methods for designing tests: - Using the Record Scenario feature, you can design the test. - Utilizing the auto test case generation capability, algoQA generates test cases based on a given feature name and user input. For iOS devices, test cases and scripts can be generated automatically using the algoQA platform. The process involves navigating to the appropriate project, and in the Test Cases pane, you can proceed to generate the scripts by clicking the Generate Scripts button. The generated scripts can be downloaded to your local folder and executed using a terminal window. Additionally, for mobile app automation using Python Squish QT (QML), test scripts can also be generated automatically after generating test cases. The process involves navigating to the appropriate project, and in the Test Cases pane, you can proceed to generate the scripts by clicking the Generate Scripts button. The generated scripts can be downloaded to your local folder and executed using a terminal window. Deciding which user flows to capture for automation from web pages scraped depends on the specific requirements of your testing project. Consider the following factors: - Business Value: Identify the user flows that have the most significant impact on your business or user experience. - Frequency: Focus on user flows that are frequently used or executed during testing. - Complexity: Prioritize user flows with a higher level of complexity, as they may require more thorough testing. - Risk: Test user flows that have a higher risk of introducing bugs or issues. - Coverage: Ensure that all essential user flows are covered in your automation suite. To get started, you can use the following steps: 1. Understand the Application: Familiarize yourself with the web application and its user flows. 2. Identify Key User Scenarios: Determine the most critical user scenarios based on business value, frequency, complexity, and risk. 3. Create a Test Plan: Develop a test plan that covers the identified user flows. 4. Implement Automated Tests: Use the algoScraper tool to extract the necessary UI elements and create automated tests for the user flows. 5. Maintain and Update Tests: Regularly review and update your automated tests to ensure they remain relevant and effective. The algorithm generates test steps based on the elements scraped from the UI and the high-level screens selected (e.g., login, home, doctor, appointment). Initially, results may not be 100% accurate, but with model training and manual edits, future accuracy improves. You can define test case steps to check specific features such as filters or doctor listings, using predefined actions like "verify content" or "verify doctors". The platform allows test design customization for such checks. By providing multiple options in the input feed for a drop-down field, the platform generates all relevant permutations automatically. You instruct it using specific notations or input conventions. You can create the algoQA offline model with wireframes or mock-up screens. Design your test cases using Prompting or the Auto test case generation option. You can generate the test scripts once the application is ready and execute. This way, you can incorporate your designs into the testing process and ensure that your automated tests align with the intended user interface. Yes, algoQA supports rich assertion capabilities, including: - Status codes - Response body validation - Headers - Business rule validations All validations are reusable, configurable, and reportable, reducing manual checks entirely. Yes, nested JSON responses can be validated including specific keys and values. Yes, algoQA supports response schema validation, ensuring: - Structural integrity - Mandatory fields - Data type correctness Yes, for REST APIs, schema configuration is currently manual, which can be challenging for very large or deeply nested responses. However, for SOAP APIs, schema validation is not manual. algoQA leverages the WSDL/XSD definitions, so the response structure and schema are automatically derived and validated, eliminating the need for manual schema configuration. The same API can be tested with multiple data sets using parameterization and dataset-driven testing (e.g., using CSV files). Validations like PAN, Aadhaar, or mobile number testing are handled using field-level validations and message categories for negative scenarios. The offline model is the input for BDD feature file generation. You can create this offline model by scraping the application under test. Once the offline model is ready, you can use the offline recorder or prompting to generate BDD feature files. Additionally, test cases can be generated using Prompting by: - Creating a Project: Start by creating a new project and adding nodes to the canvas. - Using Prompts: Describe the scenario to test in plain English (e.g., "I want to test user login with valid and invalid credentials"). - Generating Test Cases: The platform will automatically generate test cases in BDD format based on the provided prompts. Database configuration in algoQA for dynamic data-driven automation is managed through parameterized queries and secure database connections. Presently you can use User Requirements as input, and Figma/BRD is not supported. Yes, algoQA can verify whether DB updates are happening correctly. Yes. This can be handled by executing DB queries and verifying the output. Yes, algoQA can validate data at the database level. algoQA supports MongoDB, PostgreSQL, and MySQL databases. Yes. You can use customized logic (like comparing fields in an Excel spreadsheet) to validate outputs. Yes. Content can be verified against pre-set data for validation using framework native actions, or if needed, custom logic can be implemented. Yes. Yes. Yes, different datasets can be injected for different environments in algoQA. This is facilitated by the Data Decoupling option, which allows for data-driven testing and the use of separate YAML files for different environments or scripts. Yes, system-level errors such as read timeouts or connection timeouts can be simulated. Yes, different HTTP error responses (401, 403, 404, 500, etc.) can be validated. Yes, the platform supports automatic test data generation using business rules in settings. The platform enables offline/online scenario recording, prompting, conversion from legacy feature files, and defect-driven test creation. It produces scripts and automates execution across platforms. Yes, it can assess the quality of feature files, detect duplications, and help merge similar tests for more meaningful automation. Most approaches are non-intrusive and black-box. Direct code analysis is used only for coverage and missing test cases, but scenario-based black-box interactions are preferred. algoQA produces Feature Files without requiring test design by algoQA. The Auto Test Cases feature integrates with component-based design. When Feature Files are edited and saved, algoQA learns from the changes made and suggests subsequent Test Cases. For more information, refer to the [Auto Test Case Generation](https://algoshack-support.freshdesk.com/support/solutions/articles/1070000020347-auto-test-case-generation) article. Database Automation Testing is a software testing that focuses on ensuring the accuracy, completeness, security, and performance of databases within an application or system. By automating the testing process, users can efficiently verify the data integrity and identify potential risks before they escalate into major issues. You can have one Test Design for the device and reuse the same configuration for different devices. You may have to do minor changes based on requirements. Where UI differences between devices are significant, the Test Design can be lightly edited and saved as a separate copy for that device type. In other cases, differences are handled directly within test design — for example, tagging tests appropriately and using automatic device detection so the right corresponding action runs for the right variant, as was done for an ECG product with three hardware variants that each needed some variant-specific test cases.

Test Design & Data