Is this the correct approach to produce test cases on HexaWise?

  • 1
  • Question
  • Updated 3 years ago
Hi Hexawise folks.

I was "forced" :) to start an ACN internal initiative of using test automations tools for maximize the quality and optimization of the tests processes of the produts that we deliver to our clients.

In this initiative the Hexawise tool was mentioned/required for the design test tool to use.

After some studding and experiments, i have created some test cases based on manually test cases created by an colleague and by validating the already application develop flow.
Based on that functionality flow i have created parameters and values that actually references the values displayed on the screen, the sequence of pages, search forms, list results and actions (creating, editing, deleting).

With this approach í created case tests that are sequential, representing different forms/pages with dependencies between them. This resulted on creating many paired values and expend some time on auto-scripting.

Is this the correct approach for using Hexawise or should i be more abstract on representing the application test cases?

Best regards, sorry for my poor english.
Photo of Flávio


  • 1 Post
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Justin Hunter, Hexawise Founder

Justin Hunter, Hexawise Founder, Founder and CEO

  • 246 Posts
  • 15 Reply Likes

Thank you for your question.

It sounds like you are on the right track.

A couple quick suggestions:

1) check out the suggested process steps near the end of these presentation slides:

2) check out this article with "amount of detail" advice:

3) check out general advice on and

4) bounce your ideas off of more experienced colleagues at your firm; share your plan with them and have them provide feedback and ideas.

I hope these ideas help.

Photo of Aaron Ueland

Aaron Ueland

  • 7 Posts
  • 3 Reply Likes

Hey Flávio,

If you have any questions, look me up in the ACN global address book.  Happy to help out.