<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 12/03/2012 01:13 PM, Joel Madero
wrote:<br>
</div>
<blockquote
cite="mid:CAPcxoX5N74-hXvs0tnq=fz2dkwgMdT59+KRMO4SvJYGNSu3osg@mail.gmail.com"
type="cite">On Mon, Dec 3, 2012 at 7:29 AM, Petr Mladek <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:pmladek@suse.cz" target="_blank">pmladek@suse.cz</a>></span>
wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Cor,<br>
<br>
I am happy to hear from you.<br>
<br>
Cor Nouws píše v Ne 02. 12. 2012 v 23:34 +0100:<br>
> Hi all,<br>
><br>
> After the few initial mails about this, and looking at
'the' agenda, I<br>
> propose the following:<br>
><br>
> Have either<br>
> a) a LibreOffice 4.0 Test Week from Monday 10 -
Sunday 16th<br>
<br>
I am slightly scared what would happen if beta1 is not
usable in the<br>
end. Today's build still seems to work but people are still
pushing last<br>
minute features... :-)<br>
<br>
> or<br>
> b) a LibreOffice 4.0 Test marathon from Thursday 13
- Wednesday 19th<br>
<br>
We will already have freeze for beta2 at this point but it
still looks<br>
like the best compromise to me. Well, I might be to
pessimistic ;-)<br>
<br>
> (A full week from 17-23 would be to close to Xmas,
IMO).<br>
<br>
Yup, people will be busy with getting Xmas presents these
days :-)<br>
<br>
> With the promise that<br>
> - we mobilise as much people from our regular teams
to show up for<br>
> support of new-bees;<br>
> - we of course provide comprehensive, clear info to
get started;<br>
> - we focus both on random testing, scenario's and bug
triage.<br>
><br>
> By spreading it over 7 days, it's easier for people to
feel able to join :-)<br>
><br>
> Initial announcements would not be too hard. Could do
that<br>
> Monday/Tuesday (evening).<br>
> Exchange among team members for availability can be
done later this week.<br>
> Preparing info is rather easy...<br>
<br>
Sounds great. Thanks a lot for taking care of it.<br>
</blockquote>
<div><br>
</div>
<div>I'd be able to participate off and on. My wife's and my
birthday falls in that range as well as of course Christmas
stuff and a few other things. </div>
<div><br>
</div>
<div>I want to learn how to do these random tests, any
pointers? I'll also be triaging throughout this week and
focusing on bugs reported against Version 4 master/alpha</div>
<div><br>
</div>
<div><br>
</div>
<div>Regards and thanks for leading this one,</div>
<div><br>
</div>
<div>Joel</div>
</div>
<br>
P.S. Adding a few people to this one<br clear="all">
<div><br>
</div>
-- <br>
<b><font face="garamond, serif" size="4">Joel Madero</font></b>
<div>
<font face="garamond, serif">LibO QA Volunteer</font></div>
<div><font face="garamond, serif"><a moz-do-not-send="true"
href="mailto:jmadero.dev@gmail.com" target="_blank">jmadero.dev@gmail.com</a></font></div>
</div>
</blockquote>
<font face="garamond, serif"> Random tests: I could use some
pointers as well. My "specialty" is Base. I noticed that there are
only 3 random test for it, and all of them had locks. Seems to me
that there should be more than 3. There is the creation of a
database from beginning to end. What about modifying an existing
database?</font> What about connecting to a database such as
MySQL, HSQLDB, text, spreadsheet, etc.?<br>
<br>
--Dan Lewis<br>
LibO QA Volunteer<br>
</body>
</html>