Learning Center content

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

Learning Center content

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)

Email address entry when sharing projects

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 <tester.mctesterson@testing.com>

This format will work and can be used.

Some additional small UX improvements around field focusing were made.

Learning Center content

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

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.). Hexawise now recognizes the common variants for a - in numeric ranges and replaces them with a standard -.

Remembered navigation for "Rules"

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".

Learning Center update

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

Learning Center update

We have "refreshed" the content & format of the first introductory article: What Is Hexawise and How Will It Help Me?

Error when sharing a just created, brand new plan to an existing project

These are the kind of pairwise ideas that rarely end up in test plans, but are regular sources of defects in the real world.

Learning Center update

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

Special characters in notes could prevent full display of the note

Using certain special characters in the body of a test plan note could cause the display of the note to be truncated.

Automate: Comment only lines in Gherkin

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.

Handling of long test plan names

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.

Warning in bulk edit for losing value expansions

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.

Learning Center content

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

Automate: Export scripts to Robot Framework

This export selection was not working. It now is.

Copy and delete the open test plan

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.

Automate: Ability to delete your only Automate script

Before you could not delete the last remaining Automate script in a test plan, but sometimes this is desirable. Now you can.

Automate: Gherkin sample script

We made it more apparent when you just have initial, unsaved, sample Gherkin text in Hexawise Automate using a yellow explainer bar.

Support documentation and channels for learning more about Hexawise

We are continuously expanding our support documentation and channels for learning more about Hexawise.

Some of the more recent articles include:

• Toolchain integration with the example of Jira and Xray
• Guidance around Advanced Constraints
• Guidance around Expected Results
• Cross-industry success stories

We encourage you to keep track of these Recent Updates, and engage with us on LinkedIn as well.

Special character encoding in bulk edit

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.

Automate: Keyboard and mouse interaction with parameter value selection

When entering a { for parameter value selection in a Gherkin Automate script, if you then interacted with the resulting parameter name auto-complete drop down using the mouse, rather than using the keyboard, you would't get a subsequent parameter value auto-complete drop down after selecting the parameter. Now you do with either data entry method.

Hexawise Foundations Certification

We strongly encourage you to invest an hour in earning a Hexawise Foundations certification.

To use Hexawise well, you need to understand, and apply a few important test design concepts and principles. The Hexawise Foundations certification course is the fastest way to learn these skills.

The course is available to all Hexawise users after you login to Hexawise. Click on the "Certification" tab in the bottom right of the post-login landing page, or on any screen you can click the course icon in the top right of your logged in Hexawise screen, to the left of your name.

Forced interactions import file, headers

The import of forced interactions from a file into a plan was sensitive to the formatting of the headers, and it should not be. This was resolved.

Performance for users with an extremely large number of plans

It won't be noticed by most people, but if you happen to have an extremely large number of plans (many hundreds) you'll notice a much snappier initial load of Hexawise.