Changes between Version 2 and Version 3 of Obsolete/Development/Code/TestingComponents

Timestamp:

Apr 23, 2012, 9:52:30 PM (14 years ago)

Author:

munoz

Comment:

--

Obsolete/Development/Code/TestingComponents

@@ -147 +147 @@
 
 And test whatever you need to test. Simple, right?
+
+== Running the tests ==
+
+If you set up the `PERL5LIB` environment variable correctly, now all that's missing is to ask the build tools to test:
+
+{{{
+#!sh
+$ mvn test
+}}}
+
+The `test` phase is run before `package`, so you'll have your tests run whenever you create the RPMs for your component:
+{{{
+#!sh
+$ mvn package
+}}}
+
+If you want to disable these tests (for instance, a wrong `PERL5LIB`), just disable the `module-test` profile:
+
+{{{
+#!sh
+$ mvn '-P!module-test' package
+}}}
+
+== 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.