From: Shaun McDonald <[EMAIL PROTECTED]>
Subject: Re: [qa-dev] Automated GUI Testing: What is a 'global' CWS and how do 
we test it?
Date: Thu, 15 Mar 2007 13:14:52 +0000

> Now that the issue has been raised, lets look at the process to see  
> if we can improve it.

If you have some patches to fix for MacOSX, you can raise
as issue like `Build breaker for MacOSX : to be nominated cws mingw03'
and fix in this cws. This is possible, pjanik is fixing issues in such a way.

This is just my personal opinion, we (OOo community members outside
the Hamburg team) should left nomination process and RE process for
the Hamburg team. It will take several milestones to fix MacOSX porting
issue (maybe FreeBSD issues as well), but it is not a big issue of course.

> > Currently I do not know, what the numbers and colors should tell me.
> > A clear definition will help here.
> 
> +1
> As far as I can tell, red means no build product produced, and green  
> means build product produced.
> What the number of errors stands for I'm not sure. It could be that  
> this figure includes information from previous failed builds too.
> 
> Soon the information from the Buildbots (termite) will be available  
> too. I believe it would be benifical to have a date for the last  
> build to be included in the "Tinderbox Status" for each platform.  
> This will be extremely useful for when the buildbots are added.

So - buildbot is not mature at this stage to implement something as policy,
right?

I also think still we cannot perform automated GUI Testing for `global CWS'.
Automated GUI Testing outside of the Hamburg team is not mature at this
moment. We must also do something to getting better, but it will take time.

That's why at this stage, nomination process for global CWS must leave
for Hamburg team. In short, we cannot handle, and responsible for such
a big cws.

Thanks,
-- Nakata Maho ([EMAIL PROTECTED])

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to