Pedro Lino schrieb:
If all of them start pumping daily releases which one(s) should we test?
Hi,
we will have to find out. I see you are interested in QA-affairs, so you
should subscribe , where these
questions should be discussed.
Currently I install a new dev-build every 3-4 days, for m
> + https://bugs.freedesktop.org/show_bug.cgi?id=37059
This bug is a WORKSFORME, I can run the testtool and some tests no
problem with it.
I'll see what I can learn about migrating the old set of tests.
August Sodora
[email protected]
(201) 280-8138
On Wed, Nov 16, 2011 at 2:59 PM, Petr Mladek
August Sodora píše v St 16. 11. 2011 v 14:43 -0500:
> I asked this once on IRC but it seems to me that some people are
> actually using the testtool so I figured I'd ask again to a broader
> audience. Is there any interest in maintaining/cleaning up the
> testtool? If not is there a way that those
I asked this once on IRC but it seems to me that some people are
actually using the testtool so I figured I'd ask again to a broader
audience. Is there any interest in maintaining/cleaning up the
testtool? If not is there a way that those tests can be rewritten to
work in one of the other test suit
Cor Nouws píše v Pá 11. 11. 2011 v 17:40 +0100:
> Hi,
>
> As a result of the discussions, the presentation, at the LibOCon, here
> are the conclusions.
> https://wiki.documentfoundation.org/QA/Improving_QA-Release-3.5
> and the places where people can comment and show commitment.
>
> What do you
Hi,
there was too big delay before 3.4.5 bugfix release. We decided the
following changes on the last steering call[1]:
+ create 3.4.5-rc1 instead of 3.5.0-beta2
+ create 3.4.5-rc2 instead of 3.5.0-beta4
+ add 3.5.0-beta0 one week before the feature freeze
By other words:
Petr Mladek píše v St 16. 11. 2011 v 15:31 +0100:
> Rimas pointed out that testers define their platform when entering a "
> test run". It actually affects the statistics. The number of finished
> test cases is counted separately for each platform
Rimas found that also "build id#" and "locale" aff
Petr Mladek píše v St 16. 11. 2011 v 11:06 +0100:
> Sigh, my understanding of platforms was not clear. We need to differ two
> things:
>
> + we should do all tests on all platforms because the things are
> packaged different way, there are used different compilers,
> ther
Hi,
I've retired the "Windows XP SP3" tinderbox (with build times > 24
hours), and instead set up a new one, called "Windows 2008R2". Cloph -
can you please remove the "Windows XP SP3" box from the tinderbox
reports?
"Windows 2008R2" is a fairly fast machine that produces the builds in
about 3.5
Petr Mladek píše v Út 15. 11. 2011 v 19:44 +0100:
> 4. platform:
>
> + why:
>
> + some tests might depend on platform; for example the
> open/save dialogs look different way on Linux,Windows,
> and MAX; also KDE vs. GNOME
>
> + main
Yifan Jiang píše v St 16. 11. 2011 v 17:10 +0800:
> Hi all,
>
> On Wed, Nov 16, 2011 at 04:38:54PM +0800, Yifan Jiang wrote:
> > 1. Do we need components split in L10n tests?
> >
> > I have ever considered the leraning curve when l10n and function test
> > doesn't have a consistent scheme
Yifan Jiang píše v St 16. 11. 2011 v 16:38 +0800:
> Hi Petr,
>
> Thanks for the detailed summary, I hope I can review this before sending
> mine:) If I understand you correctly, scheme D ignores a requirement, doesn't
> it?
What requirement is ignored by the scheme D?
> > 7. Test run creation:
>
Hi all,
On Wed, Nov 16, 2011 at 04:38:54PM +0800, Yifan Jiang wrote:
> 1. Do we need components split in L10n tests?
>
> I have ever considered the leraning curve when l10n and function test
> doesn't have a consistent scheme. But from reconsidering, it is probably
> natural for a use
Yifan Jiang píše v St 16. 11. 2011 v 14:48 +0800:
> 4. The amount of how many localization is another concern. In the new scheme,
> for each priority we will have "7 components * 4 locale * 4 priority" (112)
> groups. If I understand it right, when there are 10 locales, the number will
> be 280 ?!
Hi Petr,
Thanks for the detailed summary, I hope I can review this before sending
mine:) If I understand you correctly, scheme D ignores a requirement, doesn't
it?
> 7. Test run creation:
>
> + requirements:
> + create test run for a given component (only Writer
>
15 matches
Mail list logo
