April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus

by Christophe Demarey

Indeed, Nautilus logic to run test differs a bit from the TestRunner logic. For example, if your test fails, it is run a second time to open a debugger but it could do side effects. Why don't you just run your tests from the test runner or using MyTestClass run: #testSelector ? We will need to clean this kind of logic that should not be part of Nautilus. Could you open a bug entry for that? Regards, Christophe. Le 21 avr. 2015 Ã 15:34, Otto Behrens a Ã©crit : > I realised I may have posted this on the wrong list. Is there anyone > that can help with this one please? > > > ---------- Forwarded message ---------- > From: Otto Behrens <otto(a)finworks.biz> > Date: Sun, Apr 19, 2015 at 10:08 AM > Subject: exception handling problem when running tests in Nautilus > To: pharo-users(a)lists.pharo.org > > > Hi, > > Thanks everyone for the new Pharo and all the work done. I like Spotter! > > I gave Pharo 4 a try today and ran into a problem with running tests > in a TestCase (test class -> run tests). I just get the debugger > popping up with WARequestContextNotFound. > > In the setUp of our test case, we call WACurrentRequestContext value, > but handle the error when we do not have a context, for example: > > [ WACurrentRequestContext value. true ] > on: WARequestContextNotFound > do: [ :e | false ] > > This handler: "[ :e | false ]" is never called. What influences this > is the exception handling in: > > AbstractNautilusUI >> #runTestsOfClass:notifying: > > Firstly, I think that it may be slighly better to call "e pass" or "e > outer" in stead of "e defaultAction", as this would give another outer > handler a chance to do something. The defaultAction is called when > there are no more outer handlers anyway. > > After trying this, it did not help my cause. And I think that this is > because the WACurrentRequestContext is a Notification and not an > Error. > > I then replaced Exception with Error in the handler in > AbstractNautilusUI. This seem to work. What also works is to > completely remove the exception handling in AbstractNautilusUI >> > #runTestsOfClass:notifying: > > What is a bit strange is the inconsistency in this exception handling > when running a suite or an individual test. Perhaps this kind of code > could be better on the TestSuite and not in the Nautilus UI? > > Can anyone please help? Should I be doing something else? > > Cheers > Otto >

April 21, 2015

Fwd: exception handling problem when running tests in Nautilus

by Otto Behrens

I realised I may have posted this on the wrong list. Is there anyone that can help with this one please? ---------- Forwarded message ---------- From: Otto Behrens <otto(a)finworks.biz> Date: Sun, Apr 19, 2015 at 10:08 AM Subject: exception handling problem when running tests in Nautilus To: pharo-users(a)lists.pharo.org Hi, Thanks everyone for the new Pharo and all the work done. I like Spotter! I gave Pharo 4 a try today and ran into a problem with running tests in a TestCase (test class -> run tests). I just get the debugger popping up with WARequestContextNotFound. In the setUp of our test case, we call WACurrentRequestContext value, but handle the error when we do not have a context, for example: [ WACurrentRequestContext value. true ] on: WARequestContextNotFound do: [ :e | false ] This handler: "[ :e | false ]" is never called. What influences this is the exception handling in: AbstractNautilusUI >> #runTestsOfClass:notifying: Firstly, I think that it may be slighly better to call "e pass" or "e outer" in stead of "e defaultAction", as this would give another outer handler a chance to do something. The defaultAction is called when there are no more outer handlers anyway. After trying this, it did not help my cause. And I think that this is because the WACurrentRequestContext is a Notification and not an Error. I then replaced Exception with Error in the handler in AbstractNautilusUI. This seem to work. What also works is to completely remove the exception handling in AbstractNautilusUI >> #runTestsOfClass:notifying: What is a bit strange is the inconsistency in this exception handling when running a suite or an individual test. Perhaps this kind of code could be better on the TestSuite and not in the Nautilus UI? Can anyone please help? Should I be doing something else? Cheers Otto

April 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-04-20 until: 2015-04-30

by stepharo

>> Hi phil >> >> just that you know what we are doing >> >> - Mathieu Lacatou an intern from Thales should be visiting the team for >> 10 days to pair program with esteban >> about the OSWindow multi-windowing support >> >> - JB and Merwan are extending the OSWindow touch support, like >> generating scroll events >> >> - JB is working on Woden and adding some shadders for 3D demoes. > I will have a new guy from Senegal starting to work tomorrow in my lab > on using GPU and Wooden for doing SPH&epidemiological modeling. > How to coordinate all these activities ? Cool :) I do not know For now he should have a look at Woden, JB planned to make a CI. But he was blocked because of a bug in the old version of Metacello that we use. So as soon as Metacello is updated, JB can continue his build. Stef >

April 21, 2015

Re: [Pharo-dev] Roadmap

by stepharo

Le 20/4/15 20:47, Dmitri Zagidulin a Ã©crit : > Sounds great. What is 'leading char'? the fact that a string encodes its language. Stef > > On Mon, Apr 20, 2015 at 1:44 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > >> Similar question - are there any roadmap plans to add Dictionary >> literals to Pharo? > We discussed about object format but right now I think that we > would like to (without thinking too much) > - take advantage of Athens > - continue to improve the tools > - put the bootstrap in production > - make SDL2 working for real and OSwindow > - clean spec > - FFI FFI FFI and again FFI > - continue the remodularisation effort > > If I would open a new work place it would be > - to integrate Xtream and get rid of the old streams. > - clean/remove leading char > > Stef > >> >> On Mon, Apr 20, 2015 at 1:20 PM, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> >> >> Le 20/4/15 16:39, Dmitri Zagidulin a Ã©crit : >>> I would love to see two things in Pharo 5: >>> >>> 1) Fix for mouse scrolling (at least on Mac OS X, though I >>> think it does the same on Linux etc) in the class pane. >>> While mouse-scrolling (either via a mouse wheel or >>> two-finger scrolling on the touchpad) through the classes, >>> the focus frequently and erratically jumps to the package >>> pane, and the package pane starts scrolling instead. The >>> focus also sometimes jumps when you reach the end of the >>> class list (and, again, the package pane starts scrolling >>> instead). >> >> Yes >> >>> >>> 2) A button in the debugger that copies the error message to >>> the clipboard (you can sort of do it currently by editing >>> the title of the error window, but that's really awkward). >> >> it should be easy to do. >> >>> >>> I also have a question. Are there currently any roadmap >>> plans for namespaces or modules for Pharo? I saw a brief >>> discussion about it a few years back >>> (http://forum.world.st/Pharo-and-Namespaces-td4636635.html >>> ), and wanted to see if it's still on the table. >> >> Yes but not for Pharo 50. >> >> Stef >>> >>> >>> >>> On Mon, Apr 20, 2015 at 2:58 AM, stepharo <stepharo(a)free.fr >>> <mailto:stepharo@free.fr>> wrote: >>> >>> Hi >>> >>> if you have suggestions please let us know. Now usually >>> suggestions often comes with time allocation ;) >>> We have definitively a list of points we want to see >>> addressed. >>> >>> Stef >>> >>> Le 19/4/15 23:19, Torsten Bergmann a Ã©crit : >>> >>> Do we have a roadmap for Pharo 5 already? >>> >>> >>> >>> >>> >>> >> >> > >

April 21, 2015

Re: [Pharo-dev] TDD and BDD

by Christophe Demarey

Le 21 avr. 2015 Ã 13:44, Sean P. DeNigris a Ã©crit : > Miguel Moquillon wrote >> BDD and TDD stands for different purposes with different actors... > > While that's unfortunately often true in practice, there is no difference > philosophically. [T|B]DD "done right" always focuses on the user. But > because of the word "test" in TDD, many tests (including many in our image) > became incomprehensible from a "how do I use this library" POV, tested > internal implementation details, etc. So BDD was invented to make the focus > on behaviors explicit and to guide us all toward best practice. It also > quite nicely unified acceptance testing and unit testing. > > The "In order to..." that you're describing is the outer, high-level > acceptance test that in Ruby for example might be written with Cucumber. But > once one has a failing acceptance test, the next step in BDD is to drop down > into e.g. RSpec and write something a lot closer to a unit test, often > mocking out collaborators to drive creation of an API. this one is often called the outside - in loop (ref: http://dannorth.net/whats-in-a-story/) Even is the outside - in loop is not used, I find valuable to encourage people to name (and write) their unit tests in terms of behavior.

April 21, 2015

Re: [Pharo-dev] Phaor 50: updating Metacello

by stepharo

> Stef, > > While in development you should be doing builds with the most recent > version on the github master branch ... that way if you hit problems > and Christophe or I have bugfixes along the way, yes > those fixes will be folded into the latest build ... I will add > Pharo5.0 to my travis testing lineup shortly ...

April 21, 2015

Re: [Pharo-dev] New Download instructions (esp. for GNU/Linux)

by stepharo

Superb! Thanks for making Pharo experience much better. Stef Le 20/4/15 21:23, Sean P. DeNigris a Ã©crit : > We revamped the download instructions to incorporate the new VM builds and > platform all-in-ones. The biggest improvement was that GNU/Linux now has its > own instruction page laying out the various options and gotchas. Of course > we should continue to improve, but IMHO we have addressed the most > persistent gotchas. > > Check out the pages: http://pharo.org/download and > http://pharo.org/gnu-linux-installation (which is linked from the first) > > Next up: we'd like to use the OpenBuildService to build from sources for all > supported GNU/Linux configurations. Help is welcome! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/New-Download-instructions-esp-for-GNU-Linux-tp4820692… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by Stephan Eggermont

On 21/04/15 14:53, Esteban Lorenzano wrote: > >> On 21 Apr 2015, at 14:37, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> On 21/04/15 13:14, Esteban Lorenzano wrote: >> >>> nope, solution is to explicit version to load :) >> >> Explicit symbolic version, that is. >> Never a fixed number, as that can't be patched. >> That breaks the update process just as well. > > noâ¦ explicit fixed number. I need version 1.0.42, not #stable or #myCoolFantasyNumberWichAfterAllIsEqualButWorstTo-1-0-42 > And of course can be patchedâ¦. with version 1.0.43. > Thatâs the only way to be able to make the update process work. The explicit version number is something you record while loading and put in a snapshot class/log. Please think through how this is supposed to work, for all stakeholders involved. Stephan

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by stepharo

@esteban Pavel is not stupid. So we could ask him what are his scenarios. @Pavel So pavel can you explain what and why you need? And yes we will have to have another level of tooling because now it can be really difficult @esteban we should add the repositories to the projects because we should be able to publish in this repositories. Else it will be again the time of the guy fixing a problem that will be consumed. Or we can also simply say to people that we do not care of their time, but I would prefer that we pay attention. In that case this is simple for me I will not fix or even look at code that is not in the main system and with this approach we will all have lost something. Stef

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by stepharo

Le 21/4/15 12:49, Esteban Lorenzano a Ã©crit : > >> On 21 Apr 2015, at 11:42, Ben Coman <btc(a)openinworld.com >> <mailto:btc@openinworld.com>> wrote: >> >> btw, how do you merge Configurations? For example, if I fix >> something "X" in my image and continue to work in it a month while >> the Image Configurations move forward, how do avoid losing that fix >> when I update to the latest Configuration ? > > you *do not* merge configurations. > if you fix something in a âconfiguredâ project, you submit your > change to proper repository (not as a SLICE, as regular packages), > which in time will be included (or not, if âproject ownerâ rejects it) > in a new configutation that will be included in Pharo. > > thatâs how any complex project worksâ¦ and thatâs how we should work > too. SLICES are just a patch that exists because our system still not > modular enough. Well in reality you will still use slice because reality is more complex than our dreams. But you are right at the conceptual point of view :) > >> >> Actually I guess it would be useful if a Configuration could be >> merged with the same GUI that merges a Slice. > > wellâ¦ monkey and integrator app (integrators use it) does the proper > loading. > But I insist: configurations are not merged: versions are loaded, > instead. > > cheers. > Esteban > >> >> cheers -ben >> >> On Tue, Apr 21, 2015 at 2:47 PM, Esteban Lorenzano >> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> >> > On 21 Apr 2015, at 08:06, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> > >> > It means that we should also add the repositories of these >> projects so that MC can merge no? >> well, but you should not merge this projects :) >> >> > >> > Le 20/4/15 22:19, Esteban Lorenzano a Ã©crit : >> >> they are handled separately, through configurations. >> >> >> >> cheers, >> >> Esteban >> >> >> >>> On 20 Apr 2015, at 21:02, Pavel Krivanek >> <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >> >>> >> >>> Hi, >> >>> >> >>> these packages do not have a version in the Pharo50 repository: >> >>> >> >>> Athens-Balloon >> >>> Athens-Cairo >> >>> Athens-CairoPools >> >>> Athens-Core >> >>> Athens-Examples >> >>> Athens-Morphic >> >>> Athens-Text >> >>> ConfigurationOfAthens >> >>> ConfigurationOfGlamourCore >> >>> ConfigurationOfGTInspectorCore >> >>> ConfigurationOfGToolkitCore >> >>> ConfigurationOfGTPlaygroundCore >> >>> ConfigurationOfGTSpotter >> >>> ConfigurationOfOSWindow >> >>> ConfigurationOfRubric >> >>> ConfigurationOfShoreLineReporter >> >>> ConfigurationOfTxText >> >>> ConfigurationOfVersionner >> >>> ConfigurationOfZincHTTPComponents >> >>> Glamour-Announcements >> >>> Glamour-Browsers >> >>> Glamour-Core >> >>> Glamour-Examples >> >>> Glamour-Helpers >> >>> Glamour-Morphic-Brick >> >>> Glamour-Morphic-Brick-Tests >> >>> Glamour-Morphic-Pager >> >>> Glamour-Morphic-Renderer >> >>> Glamour-Morphic-Theme >> >>> Glamour-Morphic-Widgets >> >>> Glamour-Presentations >> >>> Glamour-Rubric-Presentations >> >>> Glamour-Tests-Core >> >>> Glamour-Tests-Morphic >> >>> Glamour-Tests-Resources >> >>> Glamour-Tests-Rubric >> >>> GT-Inspector >> >>> GT-InspectorExtensions-Core >> >>> GT-Playground >> >>> GT-Spotter >> >>> GT-Spotter-EventRecorder >> >>> GT-SpotterExtensions-Core >> >>> GT-Tests-Inspector >> >>> GT-Tests-Playground >> >>> GT-Tests-Spotter >> >>> OSWindow-SDL2 >> >>> OSWindow-VM >> >>> Rubric >> >>> ShoreLine-Report-Core >> >>> ShoreLine-Report-Settings >> >>> ShoreLine-Report-UI >> >>> TxText-AthensTests >> >>> TxText-Model >> >>> TxText-Styler >> >>> TxTextTests-Model >> >>> Versionner-Core-Commands >> >>> Versionner-Core-Model >> >>> Versionner-Spec-Browser >> >>> Versionner-Tests-Core-Model >> >>> Zinc-HTTP >> >>> Zinc-Character-Encoding-Core >> >>> Zinc-Character-Encoding-Tests >> >>> Zinc-Resource-Meta-Core >> >>> Zinc-Resource-Meta-Tests >> >>> Zinc-Tests >> >>> Zinc-Zodiac >> >>> Zodiac-Core >> >>> Zodiac-Tests >> >>> >> >>> Cheers, >> >>> -- Pavel >> >>> >> >> >> >> >> > >> > >> >> >> >

April 21, 2015