I work at GE Corporate R&D ( http://www.crd.ge.com) in Niskayuna, NY. For
the last 7 years we and our colleagues at Kitware (http://www.kitware.com)
have been developing the Visualization Toolkit, vtk. vtk is an open source
C++ class library for doing visualization and imaging on Unix/Linux/Wintel
systems.
Over the past three years, we have developed an automated nightly build/test
process as well as a continuous build process. Each evening, we build vtk on
10 different platforms. On each platform we run over 500 image based
regression tests plus some text based tests. We also run purify, coverage
and a style checker. We keep all the results (over 2 years worth of
nightlies). Once the nightly process completes inside GE, we package the
html dashboards and export them to an external site, accessible to all.
For over a year now, we also do a continuous build. A process monitors the
external cvs repository and watches for a change. Once a change is detected,
the process update the working copy of the source, does an incremental build
and runs four smoke tests. The main purpose of the continuous is to protect
the nightly from failing because of careless checkins.
In May, I gave a talk and paper at Quality Week 2000 in San Francisco. The
majority of attendees are from traditional Software Q/A organizations. My
talk on Extreme Testing was well attended, but I got the feeling that the
audience was missing the boat.
Since then, we’ve discovered the Extreme Programming community.
Our nightly dashboard is at:
http://public.kitware.com/vtk/quality/MostRecentResults/
Our continuous dashboard is at:
http://public.kitware.com/vtk/quality/ContinuousResults/solaris/Conti…
sults.html
The current system is very vtk-centric. We are working on another open
source project for the National Library of Medicine that will use a more
portable/generic testing approach. I’ll be happy to keep this group informed
if there is interest.
Bill Lorensen
This is very cool stuff, keep it coming.
- Hide quoted text — Show quoted text -
Bill Lorensen wrote:
> I work at GE Corporate R&D ( http://www.crd.ge.com) in Niskayuna, NY. For
> the last 7 years we and our colleagues at Kitware (http://www.kitware.com)
> have been developing the Visualization Toolkit, vtk. vtk is an open source
> C++ class library for doing visualization and imaging on Unix/Linux/Wintel
> systems.
> Over the past three years, we have developed an automated nightly build/test
> process as well as a continuous build process. Each evening, we build vtk on
> 10 different platforms. On each platform we run over 500 image based
> regression tests plus some text based tests. We also run purify, coverage
> and a style checker. We keep all the results (over 2 years worth of
> nightlies). Once the nightly process completes inside GE, we package the
> html dashboards and export them to an external site, accessible to all.
> For over a year now, we also do a continuous build. A process monitors the
> external cvs repository and watches for a change. Once a change is detected,
> the process update the working copy of the source, does an incremental build
> and runs four smoke tests. The main purpose of the continuous is to protect
> the nightly from failing because of careless checkins.
> In May, I gave a talk and paper at Quality Week 2000 in San Francisco. The
> majority of attendees are from traditional Software Q/A organizations. My
> talk on Extreme Testing was well attended, but I got the feeling that the
> audience was missing the boat.
> Since then, we’ve discovered the Extreme Programming community.
> Our nightly dashboard is at:
> http://public.kitware.com/vtk/quality/MostRecentResults/
> Our continuous dashboard is at:
> http://public.kitware.com/vtk/quality/ContinuousResults/solaris/Conti...
> sults.html
> The current system is very vtk-centric. We are working on another open
> source project for the National Library of Medicine that will use a more
> portable/generic testing approach. I’ll be happy to keep this group informed
> if there is interest.
> Bill Lorensen