summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006477.html
blob: 248deb04bcfa98a9a6c6a4f73d103867acc57539 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Updates testing
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20testing&In-Reply-To=%3C20110708093939.GB21938%40mars-attacks.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="006470.html">
   <LINK REL="Next"  HREF="006479.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Updates testing</H1>
    <B>nicolas vigier</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20testing&In-Reply-To=%3C20110708093939.GB21938%40mars-attacks.org%3E"
       TITLE="[Mageia-dev] Updates testing">boklm at mars-attacks.org
       </A><BR>
    <I>Fri Jul  8 11:39:39 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="006470.html">[Mageia-dev] Updates testing
</A></li>
        <LI>Next message: <A HREF="006479.html">[Mageia-dev] Updates testing
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6477">[ date ]</a>
              <a href="thread.html#6477">[ thread ]</a>
              <a href="subject.html#6477">[ subject ]</a>
              <a href="author.html#6477">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Thu, 07 Jul 2011, andre999 wrote:

&gt;<i> nicolas vigier a &#233;crit :
</I>&gt;&gt;<i> On Thu, 07 Jul 2011, Damien Lallement wrote:
</I>&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> Le 07/07/2011 14:18, nicolas vigier a &#233;crit :
</I>&gt;&gt;&gt;&gt;<i> On Wed, 06 Jul 2011, Jos&#233; Jorge wrote:
</I>&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;&gt;<i> Le mercredi 6 juillet 2011 18:12:44, nicolas vigier a &#233;crit :
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> Hello,
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> A few package updates need testing on x86_64 (they have been tested on
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> i586, thanks to Dave Hodgins) :
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1944">https://bugs.mageia.org/show_bug.cgi?id=1944</A>
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1485">https://bugs.mageia.org/show_bug.cgi?id=1485</A>
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1892">https://bugs.mageia.org/show_bug.cgi?id=1892</A>
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1939">https://bugs.mageia.org/show_bug.cgi?id=1939</A>
</I>&gt;&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;&gt;<i> All tested, but without a testcase, some are hard to test.
</I>&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;<i> Yes, testcase need to be done for each package. Maybe we could have a
</I>&gt;&gt;&gt;&gt;<i> wiki page to save all test cases, and use them when the same package is
</I>&gt;&gt;&gt;&gt;<i> updated again ?
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> No need to put this on the wiki as it will be useless for 90% of them as an
</I>&gt;&gt;&gt;<i> update request must have a test case for the bug fixed, not for the whole
</I>&gt;&gt;&gt;<i> package.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> Yes, for the test about the bug fixed. But isn't there tests to check for
</I>&gt;&gt;<i> regressions ?
</I>&gt;<i>
</I>&gt;<i> The general idea sounds good.
</I>&gt;<i> But that would make a pretty big wiki page, if we especially if we include 
</I>&gt;<i> big apps like LibreOffice &amp; Postgresql.
</I>&gt;<i> Maybe link each bigger app to a standing bugz report for that purpose ?
</I>&gt;<i> It would be pretty hard to make even close to complete regression tests for 
</I>&gt;<i> bigger apps as well.  (imagine 599 tests for LibreOffice ...)
</I>
I think the goal is not to do full regression tests, as we don't have
time for this. But do minimal testing, in 1 or 2 minutes, to check that
basic functionality is still working, to check that the update didn't
break everything. For LibreOffice that could be opening a test document.
Most applications are easy to test. But some require knowledge of the
software, or some configuration files, to test, so we could keep a list
of test commands or things to do and config files. 

</PRE>


































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="006470.html">[Mageia-dev] Updates testing
</A></li>
	<LI>Next message: <A HREF="006479.html">[Mageia-dev] Updates testing
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6477">[ date ]</a>
              <a href="thread.html#6477">[ thread ]</a>
              <a href="subject.html#6477">[ subject ]</a>
              <a href="author.html#6477">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>