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/2011-July/006463.html | 137 +++++++++++++++++++++++++++++++ 1 file changed, 137 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006463.html (limited to 'zarb-ml/mageia-dev/2011-July/006463.html') diff --git a/zarb-ml/mageia-dev/2011-July/006463.html b/zarb-ml/mageia-dev/2011-July/006463.html new file mode 100644 index 000000000..1b8ed7626 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006463.html @@ -0,0 +1,137 @@ + + + + [Mageia-dev] Updates testing + + + + + + + + + +

[Mageia-dev] Updates testing

+ andre999 + andr55 at laposte.net +
+ Fri Jul 8 04:50:35 CEST 2011 +

+
+ +
Stew Benedict a écrit :
+> On 07/07/2011 07:38 PM, andre999 wrote:
+>>>>>> All tested, but without a testcase, some are hard to test.
+>>>>>
+>>>>> Yes, testcase need to be done for each package. Maybe we could have a
+>>>>> wiki page to save all test cases, and use them when the same
+>>>>> package is
+>>>>> updated again ?
+>>>>
+>>>> No need to put this on the wiki as it will be useless for 90% of
+>>>> them as an
+>>>> update request must have a test case for the bug fixed, not for the
+>>>> whole
+>>>> package.
+>>>
+>>> Yes, for the test about the bug fixed. But isn't there tests to check
+>>> for
+>>> regressions ?
+>>
+>>
+>> The general idea sounds good.
+>> But that would make a pretty big wiki page, if we especially if we
+>> include big apps like LibreOffice & Postgresql.
+>> Maybe link each bigger app to a standing bugz report for that purpose ?
+>> It would be pretty hard to make even close to complete regression
+>> tests for bigger apps as well. (imagine 599 tests for LibreOffice ...)
+>>
+> There once was a project at Mandriva where each packager was to supposed
+> to come up with a basic functionality test for his/her package(s),
+> although I don't think it got much traction aside from those of us who
+> were getting paid to work on the distro and whose manager made the tests
+> a deliverable.
+> iirc there was even some automation framework so they they could be run
+> by machine.
+
+That sounds like a good idea -- especially if we could implement it in a manner 
+easy to do for packagers
+
+-- 
+André
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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