In order to ensure effective testing, it is important to determine the part of functionality which brings testing the biggest effect at minimum cost. 

Consequently, it is possibly possible to increase the coverage of functionality tests.

Map function

For the optimal coverage of functionality using testing scenarios, it is advisable to create a map function.  The map function answers the question which functionality is the most critical and the most demanding in terms of testing, and which functionality has the biggest impact on business if an error occurs in this functionality.

Based on this information, the following can be created:

• criticality map function (systems x functions x criticality)
• map function of labour intensity of test data (systems x functions x labour intensity or price)
• map function of labour intensity of removing consequences (systems x functions x labour intensity or price)

Afterwards we propose testing scenarios in order to use the minimum number of steps to cover the maximum number of most important functionalities.

Creating a map function is a good step to start a project test . Implementation can be done in individual MD up to dozens of MD.

Hit map

The tool for recording errors in projects (e.g. Bugzilla, Jira etc) offers information on which functionality causes most errors. This functionality is a suitable candidate for automated testing.
It is possible to create a hit map in individual MD or dozens of MD. It will increase quality in the most troublesome parts of the system.