23.126.0 - SaaS
Guidelines
Version 23.126 Date: 18.10.2023
Empower Your Testing: Customized execution fields for tailored test case runs
Useful when:
You want to be flexible when it comes to running in agile environments where test cases may need to accommodate different data, configurations, or environments without altering the core test case template.
You need to avoid duplicating test cases for slightly different test scenarios. This not only saves time and effort but also helps maintain a cleaner and more organized test case repository, making it easier to manage and keep up-to-date.
You are required to provide more comprehensive and tailored test execution reports. By capturing information relevant to the specific run, such as device details, test environment settings, or user profiles, the QA team can offer clearer insights into the test results. This aids in faster issue identification, resolution, and overall test case improvement.
Guide: To start using this feature, begin by navigating to the project template page.
Look for the 'Test run configuration' option at the bottom, and select that tab.
By default, you'll find a single field labelled 'Tested version,' which represents the pre-defined field from before.
You can now add various custom fields (except rich text fields) to the template and define their values, just as you would for the project template.
If needed, you can group these fields to logically organize them for easier navigation.
💡Tip: Once you save the template, it will be applied to the entire project. You can export it and apply it to different projects as well later when it’s needed.
The next time you start executing a test case, you'll encounter a modal with predefined custom fields. You can select the values that are applicable to your current test run.
You can set your selection as the default, ensuring it's automatically set for future test runs. During a test execution, if you wish to change values, you can do so easily. Simply expand the block and make the necessary adjustments.
After executing a test case, you can access the information in the execution page. Just click on the 'Select column' icon (column chooser) and drag the relevant fields onto the grid.
The pertinent data will then be displayed for your review.
👉 Please note that sorting and filtering for custom fields are not supported on the grids. When running a test scenario and needing to define values for each test case, click on the column selection button, drag the necessary fields onto the grid, and set the values for each test case.
Later, when you need to create a report, you can easily include this information in one document, generating a comprehensive report effortlessly. Just select the field you want to include and adjust thelayout.
Expanding Horizons: Enriching PowerShell and Unix Shell Scripts with Variables
Useful when:
You need additional information from a test case or test scenario execution to use as variables to make Powershell or Unix Shell scripts more versatile and adaptable to a wider range of testing scenarios.
What has been added: You can utilize the following new variables that are now available in the Unix/Powershell agents:
Fields, including custom fields from Test Scenarios, similar to the already available test case fields.
TestCaseId
ProjectId (from the test case)
TestScenarioId
TestScenarioProjectId
👉 Please note, test scenario relevant variables are only available if the execution was done from the context of a test scenario. Additionally, in Unix shell agent data that is retrieved in Powershell with the callback mechanism is available as environment variables:
AQUA_TestExecutionId
AQUA_TestScenarioExecutionId
AQUA_ProcessElementExecutionId
AQUA_AgentCode
New aqua Jira plugin design that's been spruced up and improved
If you already have aqua4jira installed, you can easily update it by going to the 'Manage apps' page and selecting aqua jira app. From there, just click the 'Update' button and you're good to go. If you don’t have it installed yet, you can find it here.
Useful when:
You want to associate test cases with Jira issues to ensure that your test coverage is aligned with the project's requirements.
You want to start a test execution directly from the Jira issue, saving time and reducing the likelihood of missing critical test scenarios.
You are looking on how to streamline the test planning process and ensure comprehensive coverage of all requirements.
You need to test results and progress reported back to Jira live.
Guidelines:
To enable the aqua test cases in jira issue, simply open the ticket and click on the 3-dot menu. Then, select 'aqua test cases'.
From now on, the test cases associated with Jira issues will appear beneath the description field.
You can continue using it as usual, whether that means creating new test cases, checking test results, or initiating a new execution. 🤚 Want to know what's coming next? Keep an eye out for updates, as we're currently working on exciting changes that will take your testing experience to the next level.
Last updated