[Hudson] Regression Testing

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Hudson] Regression Testing

Marcus Denker-4

        https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3%20Regression%20Testing/

The idea is that there are lots of things that are almost never tested because the tests would take too long.
*and* because the tests do something to the image that is not wanted for a normal build.

Examples

        -> recompile everything, run tests again
        -> decompile everything to text, compile and install
        -> format everything and compile
        -> condense changes
        -> write new sources
        -> run without sources
        -> run without sources but encoded temps
        -> ..... what else???
       
The idea is that this CI Server Project runs all these
after every build, but not as part of main build (so it does not lengthen the build process).

For now, this just has one test that recompiled the image and does nothing else.

--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.


Reply | Threaded
Open this post in threaded view
|

Re: [Hudson] Regression Testing

Adrian Lienhard
Nice!

Indeed, that's very useful. These tests can quickly identify regressions that else would only be discovered after a long time.

Adrian

On Feb 6, 2011, at 15:31 , Marcus Denker wrote:

>
> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3%20Regression%20Testing/
>
> The idea is that there are lots of things that are almost never tested because the tests would take too long.
> *and* because the tests do something to the image that is not wanted for a normal build.
>
> Examples
>
> -> recompile everything, run tests again
> -> decompile everything to text, compile and install
> -> format everything and compile
> -> condense changes
> -> write new sources
> -> run without sources
> -> run without sources but encoded temps
> -> ..... what else???
>
> The idea is that this CI Server Project runs all these
> after every build, but not as part of main build (so it does not lengthen the build process).
>
> For now, this just has one test that recompiled the image and does nothing else.
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>


Reply | Threaded
Open this post in threaded view
|

Re: [Hudson] Regression Testing

Yanni Chiu
In reply to this post by Marcus Denker-4
> ->  ..... what else???

cleanUpForProduction
cleanUpForRelease


Reply | Threaded
Open this post in threaded view
|

Re: [Hudson] Regression Testing

Stéphane Ducasse
In reply to this post by Marcus Denker-4
Yesssss
I love that ;)

Stef

On Feb 6, 2011, at 3:31 PM, Marcus Denker wrote:

>
> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3%20Regression%20Testing/
>
> The idea is that there are lots of things that are almost never tested because the tests would take too long.
> *and* because the tests do something to the image that is not wanted for a normal build.
>
> Examples
>
> -> recompile everything, run tests again
> -> decompile everything to text, compile and install
> -> format everything and compile
> -> condense changes
> -> write new sources
> -> run without sources
> -> run without sources but encoded temps
> -> ..... what else???
>
> The idea is that this CI Server Project runs all these
> after every build, but not as part of main build (so it does not lengthen the build process).
>
> For now, this just has one test that recompiled the image and does nothing else.
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>


Reply | Threaded
Open this post in threaded view
|

Re: [Hudson] Regression Testing

SergeStinckwich
In reply to this post by Marcus Denker-4
Impressive !!! I like that.

On Sun, Feb 6, 2011 at 9:31 PM, Marcus Denker <[hidden email]> wrote:

>
>        https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3%20Regression%20Testing/
>
> The idea is that there are lots of things that are almost never tested because the tests would take too long.
> *and* because the tests do something to the image that is not wanted for a normal build.
>
> Examples
>
>        -> recompile everything, run tests again
>        -> decompile everything to text, compile and install
>        -> format everything and compile
>        -> condense changes
>        -> write new sources
>        -> run without sources
>        -> run without sources but encoded temps
>        -> ..... what else???
>
> The idea is that this CI Server Project runs all these
> after every build, but not as part of main build (so it does not lengthen the build process).
>
> For now, this just has one test that recompiled the image and does nothing else.
>
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
>



--
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/