Changes between Version 22 and Version 23 of Obsolete/Development/Code/TestingComponents

Timestamp:

Dec 12, 2015, 12:54:05 PM (10 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Obsolete/Development/Code/TestingComponents

@@ -240 +240 @@
 === Getting the component output displayed ===
 
-By default, all the component output produced by `$self->info()`, `$self->error()`, `$self->debug()`, `$self->verbose()` are not displayed when running the tests.
-To get it display, you can add the following line to your `~/.proverc`:
-
+By default, all the component output produced by `$self->info()`, `$self->error()`, `$self->debug()`, `$self->verbose()` *are not displayed* when running the tests. To get it displayed, use one of the following two methodds:
+
+* Pass this option from the command line when executing the test:
+{{{
+mvn -Dprove.args=-v
+}}}
+
+* Set it as your default configuration when executing the tests, adding the following line to your `~/.proverc`:
 {{{
 -v
 }}}
-Or pass this option from the command line with:
-{{{
-mvn -Dprove.args=-v
-}}}
+
+When doing the one of the actions described above, the component is run in `verbose`mode.
+
+=== Setting debug level in the component ===
+
+If you'd like to get debug message displayed to help troubleshooting a component, in addition to enabling the display of componennt output, you need to define the environment variable `QUATTOR_TEST_LOG_DEBUGLEVEL` to the appropriate debug level (1 to 5).
 
 == Conclusion ==
 
-I hope this will reduce the effort required to test Quattor code. New components should have a detailed test suite. And older components should receive one.
-
-With time, we should see less regressions and less fear to change the code in maintainable ways.
+Unit tests are critical to prevent regressions in new versions and validate new features. 
+
+New components *MUST HAVE* a detailed test suite. And older components should receive one.
+