Are you sure about the quality of your test cases?
Have you ever assessed the costs of using not optimized test cases?

Value Test Case

Are you sure about the quality of your test cases?
Have you ever assessed the costs of using not optimized test cases?

Check your test cases through VTC!

Download VTC now!
Only registered users can log in and download the program. In case you have not registered yet, just write to and you will soon receive your login credentials!
What is VTC?
Value Test Case (VTC), is a software that allows you to evaluate the quality of your test cases written in natural language. It has been designed by specialists having over 20-year experience.
Who is VTC destined to?
It has been devised for Test Managers, for all workers from test areas at a high level, and for those financially managing projects.
How does it work?
After having set our VTC and having generated a reference pattern (we suggest to use your best test cases to upload the best possible patterns), it will be possible to record new test cases into VTC for the analysis. To each of them a value between 0 and 1 (confidence value) will be assigned. Only the single-pattern version is currently available, yet we are already preparing the multi-pattern one.
What logics is it based on?
VTC uses a series of algorithms based on statistical analysis and on the analysis of natural language in English: when combined together, these two kinds of analysis result in a confidence value for each test case that has been submitted.
What results can you get?
On each test case analyzed and on the whole set of test cases, our software will provide you with a weighting value between 0 and 1, where 0 is the lowest quality possible and 1 the highest level.
These values express an indication about the quality of the single test case and about the whole set that has been analyzed. Such values are listed in a file that can thereafter be processed through some software such as Excel. Please, look at some examples of charts that can be processed and at the important insights they provide.

Value Test Case VS Man Valutation

How far is it from an appraisal produced by a human mind?

VTCvsMAN Test on a Zero Client

If you want to test our product, you can get a trial version so to analyze a few tests at a very low price. We are certain you will be really satisfied with it!

Where should it be installed? Is it safe?

VTC can be installed anywhere and the relevant data will be safe.
VTC never discloses personal data: it can be installed on any corporate virtual server. OWL Solutions will grant the licenses and install them manually, so the system can be located anywhere in the world, It can even be offline, yet no one will ever access your data.

Get your VTC now!

Write to one of our specialists at
He will offer you a tailored product!

Contexts where it can be used

You can have the software evaluate all test cases intended for a specific product, then go back to the ones that got bad marks, and be able to improve the quality of the whole set of tests: you will get a better outcome for your final product.

Case 1

Opening consulting when starting a project
Luca is a test manager who was asked to set up a test campaign for a complicated project. As his company owns a repository, from where the information about previously written test cases can be drawn, Luca decides to check the status of their quality. As an experienced test manager, Luca knows that the reliability of cases is key for a perfect analysis of the product. In fact, having a good set of trusted test cases allows him to focus on other priorities. So, he uses VTC to analyze some possible set of test cases: among the results, he chooses the cases showing a higher confidence value. Moreover, Luca knows that VTC not only selects the best cases, but it can also identify those that should be at least reviewed. In this way, he can evaluate the kind of effort needed to correct them.

Case 2

Routine inspection during a project
Carrying out a project about a robot, Bob, who is a software test manager, receives several software releases to be examined through the test cycle, as planned by his colleagues from the implementation department. This means re-running many test cases, as well as preparing and executing new cases, written on purpose. For this reason, Bob uses the VTC, in order to constantly check if the confidence level of his test cases remains positive. In fact, Bob knows that test cases, even if modified and reviewed by his team members, may not reach the required level, for several reasons. This situation could turn very critical in case of insufficient operating space to modify cases or to meet the deadlines set by the project management. Thanks to VTC, Bob can be proactive, thus determining where the necessary corrective steps are to be taken, and what the most suitable strategies are.

Case 3

Cross-check among projects
Anna is a manager of system integration: the resources needed to carry out tests on the envisaged projects require a continuous monitoring. Her test managers keep her updated with the issues to be overcome during the projects, and Anna asks them to analyze the sets of tests in each project with the VTC, using a pattern they all share. By doing so, Anna can get a more accurate point of view on the status of the employed resources for these test cases, and for the relevant campaigns. This enables her to pay more attention where it is needed.

Case 3a

Qualitative analysis for a focused maintenance of test cases
Constantly keeping test cases updated is expensive and Sara, working as quality manager, is fully aware thereof. Knowing where to intervene, wisely coordinating and planning interventions are constant challenges. The use of VTC can create an overall reference pattern, so Sara starts analyzing the sets of test cases. The results she gets enable her to carry out precise checks on those cases that haven't met the minimum requirements, so that she can considerably save time and money, in comparison with the manual procedure. This way, she will be able to keep her supervisors updated in good time, and to provide them with detailed pieces of information about the room for improvement.

Confidence level by test case - Project Alpha ‑ 26th Oct 2015
The chart shows the set of test cases analyzed according to their level of confidence. This provides some overall information about the analyzed set. With the help of the indicator (Threshold, see continuous line), we can divide the chart into two main areas; some test cases are above the threshold and some others are below it. The latter are the ones to be further analyzed before being used. The indicator of the threshold level of the expected result (see dotted line) divides the chart into two macro areas and clearly displays where cases stand. The ones on its right should all be above or at least on the selected threshold level.

Confidence level by level of criticality - Project Alpha ‑ 26th Oct 2015
The chart displays the set of test cases analyzed in relation to their level of confidence, sorted by level of concern (three levels, here), from the lowest to the highest one. It is important to notice that the level of criticality is a criterion you can choose to define, yet not indispensable for the VTC analysis; if it weren't present, this chart would look similar to chart no. 1. As already shown in chart no. 1, the threshold indicator (see continuous line) highlights here as well the two macro areas of test cases, some above and some others below the threshold. The chart also shows the indicator of the beginning of threshold level of the expected result (see dashed lines), obviously marking each level of concern.

Confidence level by mandatory distribution - Project Alpha ‑ 26th Oct 2015
The chart displays the set of test cases analyzed in relation to their level of confidence but arranged by compulsoriness of performance (here we have two cases, a “not compulsory” one and a “compulsory” one) during the test campaign. As already explained about the previous charts, here too the threshold (continuous line) helps us to immediately highlight the two macro areas with some test cases placed above and others placed below the threshold. It is important to notice that the compulsoriness of the performance of a test case is a criterion you can choose to define, yet not indispensable for the VTC analysis (as already observed in the level of criticality); if weren't present, the chart shown above would look similar to chart no. 1. Once more, there is the indicator of the beginning of threshold level of expected result (see dashed lines), obviously marking both the group of “not compulsory” cases and the group of “compulsory” ones. For a correct reading and interpretation of this chart, the same considerations expressed in chart no. 2 are valid.


Test Campaign

Activities aimed at organizing, carrying out, analyzing and providing documentary evidence of the check and the validation of any object undergoing formal checks.

Test Case

Organized list of steps to be taken in sequence, where - for each step - what to do and what kind of outcome is expected are explained.


Set of test cases that are deemed at the state of the art within the company, representing the analyzed area as good as possible. As a rule, the cases used in the Gold-Set should not be used during the following analyses.

Confidence Indicator

This is the fundamental value produced by VTC. This indicator is assigned to each test case analyzed by VTC, in comparison with the minimum threshold level of expected result. The more the value of the confidence indicator tends towards 1, the higher is the trust in it, for the reliability of the possible outcome during a test campaign.

Criticality Indicator

If necessary, you can assign to each test case the relevant criticality; if it is not indicated, VTC will ignore this indicator. The meaning of the criticality may dramatically vary, depending on the company. The number of criticality indicators is unlimited. In our examples, we have used three different levels.

Obligatory indicator

If necessary, you can assign to each test case its obligation; if not indicated VTC ignores this indicator. There isn't a limit to the number of obligatory indicators even if the indicator is basically divided into mandatory and not-mandatory. In the submitted examples we used two levels.

Indicator of the beginning of threshold level of expected result

It is the percentage value between 0 and 100, normally represented by a dashed line highlighting the position of the analyzed test cases, in comparison with the minimum threshold level and with their quantity.

Minimum threshold level

Value between 0 and 1 that allows to discriminate in relation to the value calculated by VTC if the test case is positioned above, below or exactly on the indicated threshold value. It is usually shown in the graph with a continuous line.

Model or reference model

Organized container of data extrapolated from the elaboration of a set of test cases considered state of the art in the company, normally called Gold-Set. Data are then used every time an analysis of test cases is required, this until a new model generation.

Set of test cases

Selection of test cases evaluated by VTC in a single run

OWL ready-to-use Solutions


Where are my data?