January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] destructive / regression tests

by Camillo Bruni

On 2013-01-24, at 18:16, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 24 January 2013 18:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> I've been thinking these days on how to implement regression tests. >> Obviously the core requirement is to launch a separate image and capture terminal output and/or result files. >> >> For now I will put them into a separate repository: >> >> http://smalltalkhub.com/#!/~Pharo/regression-testing >> >> Some question: >> - Is there a test ConfigurationOf* which can be used to try loading different versions / groups? >> - Is it ok to rely on OSProcess for now to run launch a separate new image? > > + 1 > we need such tests. > And actually it would be even useful to know which code crashing the > system , e.g. > we can even have a tests which succeed only if they crashing VM. yes exactly!! I even thought about doing this random code-change validation ;) 1. chose a random method (minus some uninteresting packages or only those with methods) 2. make it return a wrong value 3. run all tests 4. make sure we get an assertion failed ;)

Jan. 24, 2013

Re: [Pharo-project] [update 2.0] #20486

by Esteban Lorenzano

nope... HD package is still using PackageInfo, that's the problem... I will review it tomorrow On Jan 24, 2013, at 6:13 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > so was it an RPackage bug? or a CLI-TestRunner / HDReport problem? > > On 2013-01-24, at 18:09, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> looks like there are still some duplicates :( >> >> On Jan 24, 2013, at 6:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> package test was taking all packages, even all those who does not have any class defined, but are "super-packages"... that's why some tests where ran twice. >>> >>> On Jan 24, 2013, at 5:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>> what was caused the issue with the jenkins tests? >>>> >>>> On 2013-01-24, at 17:57, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>>> 20486 >>>>> ----- >>>>> >>>>> Issue 7316: Jenkins: Some tests are run twice >>>>> http://code.google.com/p/pharo/issues/detail?id=7316 >>>>> >>>>> Issue 6861: cmd+w is broken for explore browser >>>>> http://code.google.com/p/pharo/issues/detail?id=6861 >>>>> >>>>> Issue 7313: MCWorkingCopy querying facilities... >>>>> http://code.google.com/p/pharo/issues/detail?id=7313 >>>>> >>>>> Diff information: >>>>> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1331.diff >>>>> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.745.diff >>>>> http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.138.diff >>>>> http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.19.d… >>>>> >>>>> >>>> >>>> >>> >> >> > >

Jan. 24, 2013

Re: [Pharo-project] destructive / regression tests

by Igor Stasenko

On 24 January 2013 18:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I've been thinking these days on how to implement regression tests. > Obviously the core requirement is to launch a separate image and capture terminal output and/or result files. > > For now I will put them into a separate repository: > > http://smalltalkhub.com/#!/~Pharo/regression-testing > > Some question: > - Is there a test ConfigurationOf* which can be used to try loading different versions / groups? > - Is it ok to rely on OSProcess for now to run launch a separate new image? + 1 we need such tests. And actually it would be even useful to know which code crashing the system , e.g. we can even have a tests which succeed only if they crashing VM. -- Best regards, Igor Stasenko.

Jan. 24, 2013

Re: [Pharo-project] [update 2.0] #20486

by Camillo Bruni

so was it an RPackage bug? or a CLI-TestRunner / HDReport problem? On 2013-01-24, at 18:09, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > looks like there are still some duplicates :( > > On Jan 24, 2013, at 6:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> package test was taking all packages, even all those who does not have any class defined, but are "super-packages"... that's why some tests where ran twice. >> >> On Jan 24, 2013, at 5:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> what was caused the issue with the jenkins tests? >>> >>> On 2013-01-24, at 17:57, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> 20486 >>>> ----- >>>> >>>> Issue 7316: Jenkins: Some tests are run twice >>>> http://code.google.com/p/pharo/issues/detail?id=7316 >>>> >>>> Issue 6861: cmd+w is broken for explore browser >>>> http://code.google.com/p/pharo/issues/detail?id=6861 >>>> >>>> Issue 7313: MCWorkingCopy querying facilities... >>>> http://code.google.com/p/pharo/issues/detail?id=7313 >>>> >>>> Diff information: >>>> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1331.diff >>>> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.745.diff >>>> http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.138.diff >>>> http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.19.d… >>>> >>>> >>> >>> >> > >

Jan. 24, 2013

[Pharo-project] destructive / regression tests

by Camillo Bruni

I've been thinking these days on how to implement regression tests. Obviously the core requirement is to launch a separate image and capture terminal output and/or result files. For now I will put them into a separate repository: http://smalltalkhub.com/#!/~Pharo/regression-testing Some question: - Is there a test ConfigurationOf* which can be used to try loading different versions / groups? - Is it ok to rely on OSProcess for now to run launch a separate new image?

Jan. 24, 2013

Re: [Pharo-project] [update 2.0] #20486

by Esteban Lorenzano

looks like there are still some duplicates :( On Jan 24, 2013, at 6:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > package test was taking all packages, even all those who does not have any class defined, but are "super-packages"... that's why some tests where ran twice. > > On Jan 24, 2013, at 5:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> what was caused the issue with the jenkins tests? >> >> On 2013-01-24, at 17:57, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> 20486 >>> ----- >>> >>> Issue 7316: Jenkins: Some tests are run twice >>> http://code.google.com/p/pharo/issues/detail?id=7316 >>> >>> Issue 6861: cmd+w is broken for explore browser >>> http://code.google.com/p/pharo/issues/detail?id=6861 >>> >>> Issue 7313: MCWorkingCopy querying facilities... >>> http://code.google.com/p/pharo/issues/detail?id=7313 >>> >>> Diff information: >>> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1331.diff >>> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.745.diff >>> http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.138.diff >>> http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.19.d… >>> >>> >> >> >

Jan. 24, 2013

Re: [Pharo-project] [update 2.0] #20486

by Esteban Lorenzano

package test was taking all packages, even all those who does not have any class defined, but are "super-packages"... that's why some tests where ran twice. On Jan 24, 2013, at 5:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > what was caused the issue with the jenkins tests? > > On 2013-01-24, at 17:57, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> 20486 >> ----- >> >> Issue 7316: Jenkins: Some tests are run twice >> http://code.google.com/p/pharo/issues/detail?id=7316 >> >> Issue 6861: cmd+w is broken for explore browser >> http://code.google.com/p/pharo/issues/detail?id=6861 >> >> Issue 7313: MCWorkingCopy querying facilities... >> http://code.google.com/p/pharo/issues/detail?id=7313 >> >> Diff information: >> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1331.diff >> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.745.diff >> http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.138.diff >> http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.19.d… >> >> > >

Jan. 24, 2013

Re: [Pharo-project] [update 2.0] #20486

by Marcus Denker

On Jan 24, 2013, at 5:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > what was caused the issue with the jenkins tests? > It runs tests for package Test and then for all Test-* And it seems that the update did not fix that... > On 2013-01-24, at 17:57, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> 20486 >> ----- >> >> Issue 7316: Jenkins: Some tests are run twice >> http://code.google.com/p/pharo/issues/detail?id=7316 >> >> Issue 6861: cmd+w is broken for explore browser >> http://code.google.com/p/pharo/issues/detail?id=6861 >> >> Issue 7313: MCWorkingCopy querying facilities... >> http://code.google.com/p/pharo/issues/detail?id=7313 >> >> Diff information: >> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1331.diff >> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.745.diff >> http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.138.diff >> http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.19.d… >> >> > >

Jan. 24, 2013

Re: [Pharo-project] looking for the description of the MC file package format convention

by Dale Henrichs

Stef, Over the years I have seen all kinds of weird junk in mcz file names, including a number with embedded $(. Presumably that code was put in in self defense against a poorly formed file name in one of the repositories that Lukas was using:) Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Thursday, January 24, 2013 7:03:00 AM | Subject: Re: [Pharo-project] looking for the description of the MC file package format convention | | I found | | GoferVersionReference>>parseName: aString | | basicName | | basicName := aString last isDigit | ifTrue: [ aString ] | ifFalse: [ (aString copyUpToLast: $.) copyUpTo: $( ]. | package := basicName copyUpToLast: $-. | (package includes: $.) | ifFalse: [ branch := '' ] | ifTrue: [ | branch := package copyAfter: $.. | package := package copyUpTo: $. ]. | author := (basicName copyAfterLast: $-) copyUpToLast: $.. | versionNumber := (basicName copyAfterLast: $-) copyAfterLast: $.. | (versionNumber notEmpty and: [ versionNumber allSatisfy: [ :each | | each isDigit ] ]) | ifTrue: [ versionNumber := versionNumber asInteger ] | ifFalse: [ versionNumber := 0 ] | | Now I do not get why we have copyUpTo: $( | may be some files have ( ) | | Does anybody remember? | | Stef

Jan. 24, 2013

Re: [Pharo-project] looking for the description of the MC file package format convention

by Dale Henrichs

Jan. 24, 2013