Below, find the Release Notes for Ranorex DesignWise:
Release - Optimized Compute Option
“Optimized” compute option is now live.
As a summary,
- It won't affect the existing computations automatically. There will be a dropdown on the Scenarios screen to allow the user to select optimized, at which point they will need to fill in a text field with the word “optimize” and confirm it. This is intentional friction to ensure people don’t just try to do optimized computes by default all the time.
- It will run the computation on the same engine 50 times from 1 click, selecting the outcome with the least number of tests.
- Switching between standard and optimized resets cache - i.e. if you calculate standard, then switch to optimized, then back to standard, a new data table will be generated.
- Staying with the same compute option does not reset cache - i.e. if you calculate optimized, switch to another screen, don't do any other cache-resetting edits, switch back to optimized, the same table will be retrieved.
- The recommended flow/best practice is to utilize standard computation while the model is undergoing edits, then launch the optimized version when you are ready to export.
New
Advanced N-way Constraints released
One of our features is Constraints which can be used to exclude invalid or irrelevant combinations of parameter values from the Scenarios table. Advanced N-way constraints (where N can be 2 or higher) make it possible to create dependencies across any number of parameters which should be a significant time saver when defining complex rules and should expand your ability to apply our tool to highly conditional workflows.
Please refer to the dedicated "Advanced N-way Constraints" article in the documentation for the feature overview.
Improved
Parameterizable Test Name and Description for the Xray export option
In the previous implementation of the Xray export dialog, the Test Name field only leveraged the global variables (like Model or Feature Name) and the Description field was automatically populated in the background.
This change allows users to specify both fields leveraging not only global, but also model variables. It applies to both Manual and Automate scripting types.
The caveat: previously, the Description for Automate included the entire content of the Feature tab without any user interaction or choice. If that behavior needs to be preserved, users would need to manually copy the content from the Automate tab into the Description field during export.
New
Added an Automate script tag which will allow the number of exported scripts to match the number of rows on Scenarios (regardless of the parameters involved in the script block)
This was a pain point specific to system integration and end-to-end testing. In the previous functionality, let's say we have a Guidewire integration model. The Policy Center section has 10 parameters which result in 20 scenarios, and the Billing Center validation needs only 3 parameters. We couldn't write a separate script block like this:
Scenario: Billing Center validation
Given I navigate to policy summary in BC
When I check that P1 is <P1> and P2 is <P2>
And On the Amounts screen, premium is <Premium>
Then Validation is successful
Because it would export only the number of unique combinations between P1, P2, and Premium, which is very often less than 20. Such mismatches caused issues during transitions to test management systems for execution/reporting. That forced users to write very long scripts which were harder to analyze for feedback. Also, different parts of the e2e flow could have different execution methods (manual vs automated).
This change adds @enumerate_all tag that, if specified above the Scenario or Scenario Outline name, will make sure that the number of exported scripts matches the number of rows on the Scenarios screen, regardless of the number of parameters involved in that particular script block.
New
Added 1 more level to the asset hierarchy
Old hierarchy: Project (optional) -> Model
New hierarchy: Project (optional) -> Folder (optional) -> Model (for the avoidance of doubt, you can still put the models directly into the project)
So you should have more flexibility in terms of grouping your models. Folders can be created via the "New Test Model" dialog, "Edit Model" one, or Project level view (icon with a "+" sign).
Naming convention for Folders always includes Project Name automatically. Folders under the same project cannot have identical names.
If you select the Project, you will see all the models from all the folders on the right. If you select the Folder, you will see only the models in that folder.
If you delete a folder, it doesn't delete the models in it, it just removes them from the folder and puts them into the underlying project.
Improved
Clickable URLs are now allowed in Notes
URLs are now clickable inside any given test Model’s Notes.
New
Added Notes pop-up window
When accessing a Test Model that has Notes associated with it, you are now given a notification pop-up about the Notes existing. There is a “Don’t notify me again” checkbox in the Note pop-up if you don’t want to see the pop-up again when accessing the test model moving forward.
Fixed
Export now takes into account the strength selection from the export dialog, not the preview one.
In the past, selecting different preview and export coverage strengths for Automate-related outputs resulted in the generated file matching the preview choice, not the export one. That could cause confusion since the selection in the Export dialog is the "final" one from the user workflow standpoint. This was adjusted to make the generated file use the export strength selection.
Fixed
Resolved inconsistencies in the message about conflict handling between Forced Interactions and Constraints.
The dialog that appears when a user creates constraints contradicting forced interactions (or vice versa) has been updated to reflect the most recent terminology and represent the involved elements (forced interaction ID and constraint value/type) more precisely.
Fixed
Error when generating 1-way sets of scenarios
Resolved an issue where the warning dialog for 1-way computation strength could automatically redirect a user back to the previously generated n-way (without giving a chance to accept the warning).
Fixed
"Silent" error when using duplicate but case-sensitive model names
Resolved an issue where the validation of model naming uniqueness was case-insensitive.
I.e., a user could create a model with the name that matches another existing model (both private or both in the same project), with the only difference being the case ("TestModel" vs "testmodel").
No error was presented, but the model was not created either. The duplicate naming error will now be properly shown to the user and the "Create" button will be disabled.
Changed
UI Update
As part of the closer collaboration and consistency across Idera's toolset, we have changed the UI color scheme.
All references to "Test Plans" became "Test Models", and the dropdown next to the plan name (with Revisions, etc.) was streamlined to remove redundancy with the left vertical menu, but no functional changes otherwise.
Documentation and Certification screenshots will lag a bit from the update perspective, but we'll try to bring them up to speed asap.
If you notice any issues, please report them to support.
New
Learning Center Update
We have added the "Onboarding Checklist" article to the Getting Started section of our documentation center. Since we removed the previous leveling system, it can be challenging to figure out the best first steps in the Hexawise learning process. The new article hopefully addresses that.
Improved
Target manual auto-scripts or Automate scripts with Xray export configurations
Administrators configuring Xray exports can now flag the configuration as targeting manual auto-scripts, Automate scripts, or both (which is the default).
When exporting, the scripts that can be exported for the configuration that is selected will match this flag.
The most important element of this improvement is that it is now easier to have manual auto-scripts and Automate scripts in the same test plan and export each of them to Xray using different configurations.
Improved
Tosca Commander export with mixed folder hierarchies
Specially named parameters in the test plan can represent folders/hierarchy in the Tosca Commander export. These parameters should have just 1 value so as not to affect the generated scenarios, and they should use a parameter naming scheme that starts with a # (e.g., # Folder Name ). The number of # indicates the depth of the folder (e.g., ### This is 3 deep).
This scheme was limited to folder depth only ever staying the same or getting deeper, but not returning to a more shallow depth, but now works more flexibly and you can specify a higher depth after lower depths (for both folder names and individual parameters).
Example:
# Folder A: blank (column A in export)
Param 1: value 1, value 2, value 3 (column B)
Param 2: value 1, value 2 (column B)
## Folder A Deeper Child: blank (column B)
Param 3: value 1, value 2, value 3, value 4 (column C)
## Param 4: value 1, value 2, value 3 (column B)
# Folder B: blank (column A)
### Param 5: value 1, value 2, value 3, value 4 (column C)
Fixed
Error when exporting a test plan with no scenarios immediately after opening the plan
This issue has been resolved.
This defect is a good example of a pairwise defect caused by variation in the user’s activity. This type of parameter isn’t often modeled, but should be as it is the source of numerous real-world defects. Study defects in production in your own system to get a feel for this type of variation so you can model it effectively.
Improved
Canceling the initial 2-way scenario generation
After navigating to “Scenarios” in a test plan, the most recent scenarios are retrieved and displayed, or if there aren’t any then the generation of a 2-way set of scenarios is initiated. If you don’t want those 2-way scenarios (e.g. you want 3-way, or mixed-strength scenarios instead) and cancel the operation, there wasn’t then an ability to initiate the generation of a different set of scenarios in the UI. Now there is.
Fixed
Issue when copying a test plan containing advanced skip constraints
In a specific case of a test plan with a skip constraint that was skipping just a single parameter and a copy is made of the test plan the copy will have the skip constraint defined as skipping to the end of the plan, rather than skipping just the single parameter. This pairwise defect has been fixed.
Fixed
Previewing the last scenario in the manual auto-scripts UI
In a test plan with forced interactions, there was an error when previewing the final generated scenario in the manual auto-scripts UI. This was either a pairwise or 3-way defect depending on how you frame it. It is fixed.
Fixed
Value expansions with commas and CSV exports
In some cases, commas coming from value expansions were not properly escaped during a CSV export. This is fixed.
Fixed
Regression in CSV exporter
Some users will have seen an issue exporting some test plans into CSV format. This has been resolved.
Fixed
Stray click when using the “what kind of file” link on the new plan dialog
If you clicked the “what kind of file” link on the new plan dialog, there was a stray click registered which opened the browser’s file open dialog. This has been resolved.
Improved
Manual Auto-Scripts preview test selection table
The table that is used to select the scenario being previewed when writing manual auto-scripts has been updated to the new table style and functionality.
Improved
Accelerated handling of large test plans
We have made a couple adjustments to the scenario generation processes which will increase the speed for the large plans and also optimize the impact on overall performance.
Fixed
Missing warning message when deleting a parameter with value expansions.
When you delete a parameter with value expansions you should receive a warning that the value expansions will be deleted as well. This warning was temporarily missing.
Improved
Email address entry when sharing projects
When you share a project with colleagues in DesignWise, you specify their email address. This used to require a bare email address, and entry one-by-one. This has been significantly improved by allowing comma delimited lists of email addresses to be entered at one time, and to support a common format that you get when copying & pasting from an email client:
Tester McTesterson <tester.mctesterson@testing.com>
This format will work and can be used.
Some additional small UX improvements around field focusing were made.
Improved
Parameter value range delimiters
The syntax to provide a numeric range required a plain ASCII – character. That’s the character you’ll get typing with the keyboard, but if you happened to paste the numeric range from other tools, such as a word processor or spreadsheet, you could actually be pasting a Unicode variant of a dash (em dash, en dash, etc.). DesignWise now recognizes the common variants for a – in numeric ranges and replaces them with a standard -.
Fixed
Remembered navigation for “Rules”
DesignWise now properly remembers which sub-navigation you were last at within “Rules” and brings you back to that location in the test plan when you navigate back to “Rules”.