Test module initialization

As explained in the introductory material, the module initialization part of the UTF prepares the test module for execution, including:

	Caution
	The elementary question one should ask himself is the following: “Is there really a need for implementing the module initialisation by yourself?”

The argument against the implementation of a custom module initialization are the following:

The test tree can be easily and efficiently constructed automatically (covered in details in this section).
UTF also provides means to rename the master test suite.
Most of the command line parameters, except the ones used by the UTF, may be accessed through the master test suite
Global fixtures may provide states that can be accessed during the lifetime of the tests, with proper and controlled initialization and release. This approach covers several use case that might need the tweaking of the initialization functions, adding the robustness of the UTF in the initialization and release themselves.
If the test module is old and the need for module initialization is just driven by legacy code, then considering updating this part might be a good choice.

From the points above, if the need for module initialization is not there anymore, then you may jump directly to the automated section directly.