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.
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.
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.
Specially named parameters in the test plan can be used to represent folders / hierarchy in the Tosca Commander export. These parameters should have just 1 value so as not to effect the generated scenarios, and use a parameter naming scheme that starts with a
# 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).
# 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)
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.
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.
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.
In some cases commas coming from value expansions were not properly escaped during a CSV export. This is fixed.
Some users will have seen an issue exporting some test plans into CSV format. This has been resolved.
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.
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.
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.
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.
Artificial Intelligence and Machine Learning (AI/ML) is a rapidly growing area for test design and planning, so we have added the article explaining how to apply Hexawise in this area: How to perform testing of AI/ML-based systems with Hexawise
Seeing the scenario count in Hexawise for the first time can be eye-opening for multiple reasons, so we have added the article explaining how you can evaluate & adjust that metric: Why "test case count" can be a misleading metric in model-based testing (and what to to about it)
When you share a project with colleagues in Hexawise, 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 <firstname.lastname@example.org>
This format will work and can be used.
Some additional small UX improvements around field focusing were made.
We get quite a few questions about applying Hexawise to different types of testing, so here is the guidance related to system-to-system scenarios: How to perform system-to-system integration testing in Hexawise
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.).
Hexawise now recognizes the common variants for a
- in numeric ranges and replaces them with a standard
Hexawise 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".
We get quite a few questions about applying Hexawise to different types of testing, so here is the guidance related to end-to-end scenarios: How to perform end-to-end testing in Hexawise
We have "refreshed" the content & format of the first introductory article: What Is Hexawise and How Will It Help Me?
These are the kind of pairwise ideas that rarely end up in test plans, but are regular sources of defects in the real world.
We get quite a few questions about applying Hexawise to different types of testing, so here is the guidance related to data validation: How to perform request/response validation with Hexawise
Using certain special characters in the body of a test plan note could cause the display of the note to be truncated.
If you have lines in your Gherkin test scripts that contain only comments (lines that start with
#) they are now included in Automate's Gherkin preview panel, and in script exports. Inline comments were always included, but comment only lines were not prior to this improvement.