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 <email@example.com>
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.
Longer test plan names used to get truncated at the end of them in various places in the UI. This could make it hard to tell similarly named plans apart, since often the beginning of the plan name will be the same and the distinguishing part of the name will be at the end. In some places this was further hindered by there not being a tooltip on hover with the full, non-truncated plan name.
We audited everywhere plan names occur in the UI and switched to using middle truncation so the start and end of very long plan names are visible. We also ensured everywhere we truncate long plan names includes a tooltip with the full name on hover.
There used to be a warning when making parameter / parameter value edits using the bulk editor that would cause you to lose value expansions you defined. There was a regression that caused these warnings to no longer be provided. They are back.
We get quite a few questions about applying Hexawise to different types of testing, so here is the guidance related to APIs: How to test APIs with Hexawise
This export selection was not working. It now is.
To copy or delete the test plan you have open, you used to have to exit the plan and go to the manage plans view. Now there's a menu option to copy or delete the current plan, which should save a lot of clicks.
Before you could not delete the last remaining Automate script in a test plan, but sometimes this is desirable. Now you can.
We made it more apparent when you just have initial, unsaved, sample Gherkin text in Hexawise Automate using a yellow explainer bar.
We are continuously expanding our support documentation and channels for learning more about Hexawise.
Some of the more recent articles include:
We encourage you to keep track of these Recent Updates, and engage with us on LinkedIn as well.
Certain special characters would show up as Unicode encoded, rather than as the Unicode character, when editing parameters using bulk edit. This is now resolved.