From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2013-January/021129.html | 105 ++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/021129.html (limited to 'zarb-ml/mageia-dev/2013-January/021129.html') diff --git a/zarb-ml/mageia-dev/2013-January/021129.html b/zarb-ml/mageia-dev/2013-January/021129.html new file mode 100644 index 000000000..3da665f13 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/021129.html @@ -0,0 +1,105 @@ + + + + [Mageia-dev] Regression testing for generated RPM + + + + + + + + + +

[Mageia-dev] Regression testing for generated RPM

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Fri Jan 4 10:28:26 CET 2013 +

+
+ +
Le 04/01/2013 10:15, Jochen Breuer a écrit :
+>
+>
+> 2013/1/4 Guillaume Rousse <guillomovitch at gmail.com
+> <mailto:guillomovitch at gmail.com>>
+>
+>     We already run existing tests suite during package build... Running
+>     them again on a different host would just change the execution
+>     environment to use runtime dependencies instead of build time
+>     dependencies. I don't know if the potential results are worth the
+>     additional infrastructure needed.
+>
+>
+> I was under the impression, that only some kind of lint checking of the
+> RPM was performed. I'm talking about checking the functionality of the
+> packaged software. Are you already doing that? What kind of tests are
+> performed during packaging?
+Running 'make check', or 'make test', or any other software test suite. 
+Just check for %check section in package spec file, for instance:
+http://svnweb.mageia.org/packages/cauldron/python/current/SPECS/python.spec?revision=278990&view=markup
+
+-- 
+BOFH excuse #66:
+
+bit bucket overflow
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1