1

I am making changes to a configuration tool for a web application. The tool allows internal users to configure messages and custom experiences for external users of the webapp.

I have been given a task to provide cases that would show 100% test coverage, and then help the test team target reasonable test coverage for the changes. I'm trying to find a tool that will let me put configuration variations in a table or spreadsheet, and then generate the different use case variations that result from these configurations.

Does such a tool exist?

1

I'd suggest using a modelling tool to perform Model-based testing; we use one called Direct-to-test (DTT) at our workplace. Basically, you can set up a path through the application and specify what should vary based on what configuration files, proving therefore that you've covered every configuration file option (usually a cluster of nodes at the beginning of the model) and every path through the application, and let the tool generate the test cases from that. It's not a spreadsheet, but it can be easier to show people outside your department a graphic than a spreadsheet anyway.

| improve this answer | |
  • Can you please share the link to DTT download. Also the full form of DTT please. – Aravind R. Yarram Apr 2 '13 at 3:08
  • @Pangea I actually only found out the full name a couple weeks ago, but I've edited it in – Yamikuronue Apr 3 '13 at 11:22
0

Hexawise is one of several tools that could help you:

  • Identify all the potential configurations for a given system
  • Identify a prioritized set of permutations that maximize coverage (based on user-specified coverage objectives).

As dzieciou mentioned, and provided links to above, multiple tools can do this.

Disclaimer, I am the CEO of Hexawise.

Having said that, for what it is worth, here is how the process works:

First, identify the different possible configuration options that might exist in the system you are testing. Also, if relevant, you may want to include actions that users of the system might take, different data possibilities, etc.

enter image description here

Second, click on "Create Tests" or the equivalent. That will bring up a set of highly varied, prioritized permutations. In this case, the default strength is to provide the smallest possible set of scenarios that would provide you with what is known as "pairwise" or "all pairs" coverage.

enter image description here

Third, if you have a higher coverage goal (e.g., "all possible permutations"), you can select the appropriate coverage goal. Here, there are 6 parameters, so 6-way coverage would create a list of all 216 possible permutations.

enter image description here

It is worth noting that 2-way solutions will tend to find the significant majority of defects. 3-way and higher strength will tend to find very few, if any. There is a lot of literature on this topic and quite a few studies.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.