- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Problem with zinc 2.9.2

by Sven Van Caekenberghe

Norbert, I did (on macOS): $ mkdir pharo61 $ cd pharo61/ $ curl get.pharo.org/61+vm | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3036 100 3036 0 0 24386 0 --:--:-- --:--:-- --:--:-- 24483 Downloading the latest 61 Image: http://files.pharo.org/get-files/61/pharo.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/get-files/61/pharo-mac-stable.zip pharo-vm/Pharo.app/Contents/MacOS/Pharo Downloading PharoV61.sources: http://files.pharo.org/get-files/61/sources.zip Creating starter scripts pharo and pharo-ui $ ./pharo-ui Pharo.image I loaded ConfigurationOfZincHTTPComponents via the Catalog, but since that was not the latest, I loaded it manually and did ConfigurationOfZincHTTPComponents project latestVersion load. Here is the Transcript Loading 2.8.3 of ConfigurationOfZincHTTPComponents... Fetched -> Zodiac-Core-SvenVanCaekenberghe.42 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zodiac-Tests-SvenVanCaekenberghe.13 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.29 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-FileSystem-SvenVanCaekenberghe.12 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-HTTP-SvenVanCaekenberghe.453 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Zodiac-SvenVanCaekenberghe.36 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Loaded -> Zodiac-Core-SvenVanCaekenberghe.42 --- http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache Loaded -> Zodiac-Tests-SvenVanCaekenberghe.13 --- http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache Loaded -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.29 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-FileSystem-SvenVanCaekenberghe.12 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-HTTP-SvenVanCaekenberghe.453 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Zodiac-SvenVanCaekenberghe.36 --- http://mc.stfx.eu/ZincHTTPComponents --- cache ...finished 2.8.3 Loading 2.9.2 of ConfigurationOfZincHTTPComponents... Fetched -> Zodiac-Core-TorstenBergmann.48 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zodiac-Tests-SvenVanCaekenberghe.22 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zodiac-Extra-SvenVanCaekenberghe.8 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac Fetched -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-FileSystem-SvenVanCaekenberghe.15 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-HTTP-SvenVanCaekenberghe.474 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Tests-SvenVanCaekenberghe.245 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Zodiac-SvenVanCaekenberghe.44 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Fetched -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents Loaded -> Zodiac-Core-TorstenBergmann.48 --- http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache Loaded -> Zodiac-Tests-SvenVanCaekenberghe.22 --- http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache Loaded -> Zodiac-Extra-SvenVanCaekenberghe.8 --- http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache ZnBase64Encoder (DefaultInverse is Undeclared) ZnBase64Encoder (DefaultAlphabet is Undeclared) ZnSimplifiedByteEncoder class>>initializeByteTextConverters (ByteTextConverters is Undeclared) ZnSimplifiedByteEncoder class>>initializeByteTextConverters (ByteTextConverters is Undeclared) ZnSimplifiedByteEncoder class>>initializeByteTextConverters (ByteTextConverters is Undeclared) ZnSimplifiedByteEncoder class>>byteTextConverters (ByteTextConverters is Undeclared) Loaded -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-FileSystem-SvenVanCaekenberghe.15 --- http://mc.stfx.eu/ZincHTTPComponents --- cache ZnSingleThreadedServer class>>adoptAsDefault: (Default is Undeclared) ZnSingleThreadedServer class>>initialize (Default is Undeclared) ZnSingleThreadedServer class>>default (Default is Undeclared) ZnSingleThreadedServer class>>stopDefault (Default is Undeclared) ZnSingleThreadedServer class>>stopDefault (Default is Undeclared) ZnSingleThreadedServer class>>stopDefault (Default is Undeclared) ZnSingleThreadedServer class>>defaultOn: (Default is Undeclared) ZnSingleThreadedServer class>>defaultOn: (Default is Undeclared) ZnSingleThreadedServer class>>defaultOn: (Default is Undeclared) Loaded -> Zinc-HTTP-SvenVanCaekenberghe.474 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Tests-SvenVanCaekenberghe.245 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Zodiac-SvenVanCaekenberghe.44 --- http://mc.stfx.eu/ZincHTTPComponents --- cache Loaded -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 --- http://mc.stfx.eu/ZincHTTPComponents --- cache ...finished 2.9.2 (The Undeclared references are eventually resolved). The code you mentioned is present in the image. Unit tests (apart from one) are green. === Name: Zinc-FileSystem-SvenVanCaekenberghe.15 Author: SvenVanCaekenberghe Time: 14 March 2018, 2:08:47.155993 pm UUID: 9c55f9cf-c023-0d00-9b4a-76f3014de7ca Ancestors: Zinc-FileSystem-SvenVanCaekenberghe.14 === Sven > On 6 Jul 2018, at 12:50, Norbert Hartl <norbert(a)hartl.name> wrote: > > Bump. I wonder nobody sees the problem. Or do I misunderstand there is something wrong in pharo? > > Norbert > >> Am 05.07.2018 um 09:09 schrieb Norbert Hartl <norbert(a)hartl.name>: >> >> Ok, >> >> I think Iâve found something. If you look at the screenshot (that is my image from jenkins, 6.1 with my code loaded and that throw the error) you can see that Zinc-FileSystem.15 is already loaded. But the Author gives the hint that this was loaded by the image integrator. And it differs from the .15 from Svenâs repo. Exactly the difference that could cause my error. Iâm not sure if metacello upgrades only packages that have a higher version number. But that would be the explanation why it doesnât work for me. I checked it by download a fresh 6.1 image and the situation is the same here. >> So reproducing the problem should be as easy as creating a baseline that loads zinc 2.9.2 and later something from github. My case was that in the first step the project code was loaded in the image including zinc 2.9.2. That image was saved and on the next invocation it loads the test code and parasol was the first dependency to load from github and it failed. >> >> Norbert >> >> <Bildschirmfoto 2018-07-05 um 08.59.10.png> >> >>> Am 05.07.2018 um 08:44 schrieb Max Leske <maxleske(a)gmail.com>: >>> >>> On 4 Jul 2018, at 23:00, Norbert Hartl wrote: >>> >>>>> Am 04.07.2018 um 17:52 schrieb Max Leske <maxleske(a)gmail.com>: >>>>> >>>>> Hi Norbert, >>>>> >>>>> Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? >>>>> >>>> I cannot give away the image, sorry. I can try to reproduce it somehow. >>>> Do you expect the method to be there? >>> >>> I would have, yes. But as you have discovered, the problem may lie with ZnFileSystemUtils (although I would have expected that package to be updated along with Zinc). >>> >>> Max >>> >>>> >>>> Norbert >>>>> Max >>>>> >>>>>> On 4 Jul 2018, at 17:30, Norbert Hartl wrote: >>>>>> >>>>>> I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log >>>>>> >>>>>> Loading baseline of BaselineOfMobilityMap... >>>>>> ...RETRY->BaselineOfParasol >>>>>> ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: >>>>>> [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: >>>>>> ZnClient>>downloadEntityTo: >>>>>> ZnClient>>downloadTo: >>>>>> IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: >>>>>> >>>>>> The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. >>>>>> >>>>>> I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Norbert >>>>> >>> >> >

July 6, 2018

Re: [Pharo-dev] Problem with zinc 2.9.2

by Norbert Hartl

Bump. I wonder nobody sees the problem. Or do I misunderstand there is something wrong in pharo? Norbert > Am 05.07.2018 um 09:09 schrieb Norbert Hartl <norbert(a)hartl.name>: > > Ok, > > I think Iâve found something. If you look at the screenshot (that is my image from jenkins, 6.1 with my code loaded and that throw the error) you can see that Zinc-FileSystem.15 is already loaded. But the Author gives the hint that this was loaded by the image integrator. And it differs from the .15 from Svenâs repo. Exactly the difference that could cause my error. Iâm not sure if metacello upgrades only packages that have a higher version number. But that would be the explanation why it doesnât work for me. I checked it by download a fresh 6.1 image and the situation is the same here. > So reproducing the problem should be as easy as creating a baseline that loads zinc 2.9.2 and later something from github. My case was that in the first step the project code was loaded in the image including zinc 2.9.2. That image was saved and on the next invocation it loads the test code and parasol was the first dependency to load from github and it failed. > > Norbert > > <Bildschirmfoto 2018-07-05 um 08.59.10.png> > >> Am 05.07.2018 um 08:44 schrieb Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: >> >> On 4 Jul 2018, at 23:00, Norbert Hartl wrote: >> >>>> Am 04.07.2018 um 17:52 schrieb Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: >>>> >>>> Hi Norbert, >>>> >>>> Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? >>>> >>> I cannot give away the image, sorry. I can try to reproduce it somehow. >>> Do you expect the method to be there? >> >> I would have, yes. But as you have discovered, the problem may lie with ZnFileSystemUtils (although I would have expected that package to be updated along with Zinc). >> >> Max >> >>> >>> Norbert >>>> Max >>>> >>>>> On 4 Jul 2018, at 17:30, Norbert Hartl wrote: >>>>> >>>>> I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log >>>>> >>>>> Loading baseline of BaselineOfMobilityMap... >>>>> ...RETRY->BaselineOfParasol >>>>> ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: >>>>> [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: >>>>> ZnClient>>downloadEntityTo: >>>>> ZnClient>>downloadTo: >>>>> IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: >>>>> >>>>> The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. >>>>> >>>>> I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. >>>>> >>>>> Any ideas? >>>>> >>>>> Norbert >>>> >> >

July 6, 2018

MethodAnnouncements not fired on anonymous subclasses

by Peter UhnÃ¡k

Hi, I'm porting some of my code from P5, and it seems that MethodAnnouncements are no longer being fired on anonymous subclasses. Is this a bug or a feature? script: ~~~~~~~~~~~~~~~ normalCls := Object subclass: #Something. anonymousCls := normalCls newAnonymousSubclass. normalCls removeSelector: #meNormal. self logCr: ''. methodAdded := [ :method | self log: method; log: ' '; logCr: method method printString ]. methodModified := [ :method | self log: method; log: ' '; logCr: method method printString ]. SystemAnnouncer uniqueInstance weak when: MethodAdded send: #value: to: methodAdded; when: MethodModified send: #value: to: methodModified. anonymousCls compile: 'meAnn ^ ''add'''. anonymousCls compile: 'meAnn ^ ''change'''. normalCls compile: 'meNormal ^ ''add/change'''. SystemAnnouncer uniqueInstance unsubscribe: methodAdded. SystemAnnouncer uniqueInstance unsubscribe: methodModified. ~~~~~~~~~~~~~~~ P5 transcript: ~~~~~~~~~~~~~~~ a MethodAdded a subclass of Something>>#meAnn a MethodModified a subclass of Something>>#meAnn a MethodAdded Something>>#meNormal a MethodModified Something>>#meNormal ~~~~~~~~~~~~~~~ P6 + P7 transcript: ~~~~~~~~~~~~~~~ a MethodAdded Something>>#meNormal a MethodModified Something>>#meNormal ~~~~~~~~~~~~~~~ Thanks, Peter

July 6, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] New Academic Partner: ENIT

by Alexandre Bergel

Congrat Cedric for your position! Alexandre > On Jul 4, 2018, at 1:33 PM, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > First of all, thanks for the introduction Marcus. > > Just that people know, and to introduce myself, Iâm CÃ©drik BÃ©ler, associate professor at ENIT (Nation Engineering School of Tarbes). > > ENIT is a French generalist engineering school in Tarbes (southwest of France). > > <PastedGraphic-5.png> > > Iâm very happy that ENIT is now part of the consortium as academic member. > > Pharo and Smalltalk have been a huge source of inspiration for me during my PHD back in 2004/2008, so Iâm really happy to have a more concrete participation now. > > My objectives are of two kind: > (1) use Pharo as a digital workbench to teach engineering students and experiment ICT trends like IoT (PharoThings/Pi3/PiZero/ESP32), AI, web applications (client/server, MQTT, API usage with Zinc, web scrapping with XPATH and Zinc and Neoâ¦). > (2) use Pharo for my research to prototype Cyber-Physical Systems (mainly in the field of predictive maintenance) and Distributed Information Systems (called Singular Information System). > > Iâll give a talk at ESUG as an experience feedback for point (1). > > In the future, Iâll present our research development around CPSâs. > > Iâm also interested in developing a local user group. Some students get interested. In Biarritz, ESTIA, I also have some common interest in developing such CPS researches/platforms. If people from this area are using Pharo/Smalltalk, please do not hesitate to contact me. > > To conclude, Iâm interested in plenty of Pharo sub-projects like (non exhaustive list): > - The web/network stack (Zinc, Zodiac, Neo, XPathâ¦) > - PharoThings > - Bloc/Brick/Roassal > - Wooden3D (VR and AR) > - Workflow > - Distributed networking (opportunistic, MESH, discovery, â¦) > > See you soon over there, > > Cheers, > > CÃ©drick BÃ©ler > ENIT associate professor > Discord: cedreek#8178 > > >> Le 4 juil. 2018 Ã 11:27, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : >> >> [ANN] New Academic Partner: ENIT >> >> The Pharo Consortium is very happy to announce that ENIT has joined as a Academic Partner. >> >> About >> - ENIT Ecole Nationale d'ingÃ©nieurs de Tarbes: http://www.enit.fr >> - Pharo Consortium: http://consortium.pharo.org >> >> The goal of the Pharo Consortium is to allow companies and institutions to >> support the ongoing development and future of Pharo. >> >> Individuals can support Pharo via the Pharo Association: >> >> http://association.pharo.org >

July 5, 2018

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

by Julien

Thanks for all your answers, Iâm collecting these projects for the experiment. :-) Peter, > Le 5 juil. 2018 Ã 21:12, Peter UhnÃ¡k <i.uhnak(a)gmail.com> a Ã©crit : > > Hi, > > can you please include in the README at the very least how it should be launched? Looking through the code I eventually found that there's a world menu entry... but that's not exactly the best way to discovery. Yeah, the GitHub repository is not yet in a good state, the previous mail was not an announcement for the project in fact, I just put the link to show it exists, itâs realâ¦ :-) Anyway, you can run it (without the GUI, because there are some bugs in it and I do not focus too much on it for now) using this: [RottenTestsFinder analyze: (RPackage organizer packageNamed: 'Collections-Tests')] on: Warning do: #resume. > > I've ran it on couple of projects, but it didn't show anything apart from self skip, but if you find something else, I'd be interested to see what it can detect. In Collection tests you have some rotten tests. :-) BUT, the result are not totally correct right now, it is still under development so do not expect it to work for now. > > https://github.com/peteruhnak?utf8=%E2%9C%93&tab=repositories&q=&type=sourc… <https://github.com/peteruhnak?utf8=%E2%9C%93&tab=repositories&q=&type=sourc…> > > > Also when I filter packages and select one, the test cases list contains some random unrelated tests. When the filtering is not on, the test cases are correct. Yeah, I know this bug, the filter of the Spec widget does not work as I expected. If you do not use the filters, it should work well. You can select all tests in the second list using Cmd+a. Cheers, Julien

July 5, 2018

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

by Peter UhnÃ¡k

Hi, can you please include in the README at the very least how it should be launched? Looking through the code I eventually found that there's a world menu entry... but that's not exactly the best way to discovery. I've ran it on couple of projects, but it didn't show anything apart from self skip, but if you find something else, I'd be interested to see what it can detect. https://github.com/peteruhnak?utf8=%E2%9C%93&tab=repositories&q=&type=sourc… Also when I filter packages and select one, the test cases list contains some random unrelated tests. When the filtering is not on, the test cases are correct. Cheers, Peter On Thu, Jul 5, 2018 at 7:16 PM, Max Leske <maxleske(a)gmail.com> wrote: > Fuel: https://github.com/theseion/Fuel > Seaside: https://github.com/SeasideSt/Seaside > > On 5 Jul 2018, at 16:31, Serge Stinckwich wrote: > > > > On Thu, Jul 5, 2018 at 3:24 PM Julien <julien.delplanque(a)inria.fr> wrote: > >> Hello Pharo community, >> >> I am currently working on detecting rotten tests in Pharo projects. >> >> Rotten tests are defined as test methods containing one or many >> assertions in their source code but one or many of these assertions are not >> executed when the test is run. >> To have more details on the subject, you can check the research report >> related to our first definition of these tests freely available on HAL [1]. >> >> In this context, we built a test analyser which, given a Pharo package >> containing tests, finds rotten tests [2]. This analyser is still under >> development. >> >> We would like to extend the experiment of our research report [1] and to >> analyse more projects in order to get a better understanding of rotten >> tests. >> >> To do that, we need your help. You can help us in two ways: >> 1. Answer this email with links to one or many open-source Pharo projects >> containing tests. >> > > âWe have 774 tests in PolyMath: > https://github.com/PolyMathOrg/PolyMath > > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally for > machines to execute."http://www.doesnotunderstand.org/ > >

July 5, 2018

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

by Max Leske

Fuel: https://github.com/theseion/Fuel Seaside: https://github.com/SeasideSt/Seaside On 5 Jul 2018, at 16:31, Serge Stinckwich wrote: > On Thu, Jul 5, 2018 at 3:24 PM Julien <julien.delplanque(a)inria.fr> > wrote: > >> Hello Pharo community, >> >> I am currently working on detecting rotten tests in Pharo projects. >> >> Rotten tests are defined as test methods containing one or many >> assertions >> in their source code but one or many of these assertions are not >> executed >> when the test is run. >> To have more details on the subject, you can check the research >> report >> related to our first definition of these tests freely available on >> HAL [1]. >> >> In this context, we built a test analyser which, given a Pharo >> package >> containing tests, finds rotten tests [2]. This analyser is still >> under >> development. >> >> We would like to extend the experiment of our research report [1] and >> to >> analyse more projects in order to get a better understanding of >> rotten >> tests. >> >> To do that, we need your help. You can help us in two ways: >> 1. Answer this email with links to one or many open-source Pharo >> projects >> containing tests. >> > > âWe have 774 tests in PolyMath: > https://github.com/PolyMathOrg/PolyMath > > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally > for > machines to execute."http://www.doesnotunderstand.org/

July 5, 2018

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

by Serge Stinckwich

On Thu, Jul 5, 2018 at 3:24 PM Julien <julien.delplanque(a)inria.fr> wrote: > Hello Pharo community, > > I am currently working on detecting rotten tests in Pharo projects. > > Rotten tests are defined as test methods containing one or many assertions > in their source code but one or many of these assertions are not executed > when the test is run. > To have more details on the subject, you can check the research report > related to our first definition of these tests freely available on HAL [1]. > > In this context, we built a test analyser which, given a Pharo package > containing tests, finds rotten tests [2]. This analyser is still under > development. > > We would like to extend the experiment of our research report [1] and to > analyse more projects in order to get a better understanding of rotten > tests. > > To do that, we need your help. You can help us in two ways: > 1. Answer this email with links to one or many open-source Pharo projects > containing tests. > âWe have 774 tests in PolyMath: https://github.com/PolyMathOrg/PolyMath -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

July 5, 2018

Need help to get a list of Pharo projects with tests

by Julien

Hello Pharo community, I am currently working on detecting rotten tests in Pharo projects. Rotten tests are defined as test methods containing one or many assertions in their source code but one or many of these assertions are not executed when the test is run. To have more details on the subject, you can check the research report related to our first definition of these tests freely available on HAL [1]. In this context, we built a test analyser which, given a Pharo package containing tests, finds rotten tests [2]. This analyser is still under development. We would like to extend the experiment of our research report [1] and to analyse more projects in order to get a better understanding of rotten tests. To do that, we need your help. You can help us in two ways: 1. Answer this email with links to one or many open-source Pharo projects containing tests. 2. If you want, provide us private projects or, at least, run our analyser on these private projects and give us back the results. If you want to help us with the second option, send me a mail directly at julien.delplanque(a)inria.fr <mailto:julien.delplanque@inria.fr>. Thanks in advance. Regards, Julien Delplanque Links: [1]: https://hal.archives-ouvertes.fr/hal-01819302 <https://hal.archives-ouvertes.fr/hal-01819302> [2]: https://github.com/juliendelplanque/RottenTestsFinder/ <https://github.com/juliendelplanque/RottenTestsFinder/> --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

July 5, 2018

[Pharo 7.0-dev] Build #1117: 22236-User-friendly-AnnouncergtInspectorSubscriptionsIn-extension

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1117 was: SUCCESS. The Pull Request #1622 was integrated: "22236-User-friendly-AnnouncergtInspectorSubscriptionsIn-extension" Pull request url: https://github.com/pharo-project/pharo/pull/1622 Issue Url: https://pharo.fogbugz.com/f/cases/22236 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 5, 2018