Enhance test plan section with an expected results tab

  • 1
  • Idea
  • Updated 8 years ago
  • Implemented
A lot of times in our tests, we have expected results that will need to match the parameters used in creating the test. So, there should be some way of scripting it.
Photo of tanmay.bhide


  • 10 Posts
  • 0 Reply Likes
  • happy

Posted 8 years ago

  • 1
Photo of Justin Hunter, Hexawise Founder

Justin Hunter, Hexawise Founder, Founder and CEO

  • 246 Posts
  • 15 Reply Likes
Official Response

Thank you for your suggestion. We really appreciate user feedback. Please let us know if the approach described below would meet your needs.

We are planning on implementing this feature (at least partially) but do not have a estimated deadline for implementing it. If more people "like" your suggestion, we will prioritize it and get it done relatively sooner.

What we are planning to do is to in this area is to include the ability for you (using an enhanced "auto-scripting" feature) to document simple expected results (e.g., "if user includes a valid 4-digit security code, then Expected Result = customer is taken to the order confirmation screen; otherwise, an error message appears with specific instructions to resolve the problem."

I say "partially" because we do not have any plans at this time to allow users to enter in highly complex expected results (e.g., "if a customer has an income of >$250,000 and a Credit Rating of >780 and the user is requesting a mortgage of $500,000 or less in the State of New York for a property type of condo or a duplex apartment, and the applicant is not a bank employee then the Expected Result = the mortgage application should be approved at a rate of X%.")

We anticipate that this future feature enhancement will address the significant majority of Expected Results that users will want to create but will not introduce the problem alluded to in the mortgage example (where users would be required to add a lot of business logic into Hexawise in order to generate Expected Results). We want to avoid that scenario because it would require too much work for Hexawise users and because it would increase the risk that users would make errors in interpreting and entering complex business logic.

Does our planned approach seem like it would meet your needs?

Please keep your suggestions coming.

Thanks again.

- Justin
Photo of tanmay.bhide


  • 10 Posts
  • 0 Reply Likes
That works for the majority of the test cases and would be great to have it integrated in the test script section.

For complex test cases, what I am doing currently is exporting the plan to excel and then creating my expected with formulas in excel.