|
|
Boost Testing : |
From: Misha Bergal (mbergal_at_[hidden])
Date: 2005-03-09 19:07:36
Rene Rivera <grafik.list_at_[hidden]> writes:
> Misha Bergal wrote:
>> Rene Rivera <grafik.list_at_[hidden]> writes:
>> --text follows this line--
>> Rene Rivera <grafik.list_at_[hidden]> writes:
>>
>>>All,
>>>
>>>I've been reading all the testing related post and not having time to
>>>respond to them. So I decided to talk about what might be done to
>>>improve things in one big posting.
>>>
>>>For along time now one of my objectives has been to use BuildBot
>>>(http://buildbot.sf.net/) to improve the management of running the
>>>regression tests. For those who don't feel like reading about that
>>>software here's a quick summary:
>>>
[...]
>
>> 2. I still don't understand:
>> * What exactly will BuildBot tell slaves to build.
>
> It gives the slaves a sequence of command invocations. The slaves run
> those commands, and respond back to the server with the command
> output. The server puts a sequence of commands together to constitute
> a "Build". Each one of the boxes you see above the "Build" box is one
> of those commands. Follow one of the "log" links on those boxes and
> you see the command and it's output.
I am sorry, I still don't understand. What will be those commands?
What will be their results? How would we decide what toolsets to use?
How would we decide what tests to run? What do we need to know about
the slave to correctly issue the commands? What means "failed" or
"succeded" for commands? Result code is not very helpful if there are
some known failing tests.
-- Misha Bergal MetaCommunications Engineering