March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Phexample / new test framework (was: FileSystem-Git status update 2)

by Max Leske

On 20.03.2014, at 14:33, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Max Leske wrote >> rewriting our tests with SUnit, moving away from Phexample (for several >> reasons) > > I'm curious about those reasonsâ¦ I think that Phexample is pretty cool and I enjoyed writing tests with it (yes, devs donât usually say that about writing tests :) ). As Esteban said, we donât want to introduce the dependency to Phexample because of the integration. But that is only one reason. Personally I have three issues with Phexample: 1. the more complex a project becomes, the more complex the dependencies between tests get (in my case, chain lengths of 8 - 10). Problems this causes: 1.a there is no visual cue for the dependencies, so you have to try your best with protocols and naming but it just gets very confusing 1.b it becomes more likely to introduce cycles (which often crash your imageâ¦) 1.c it becomes more likely to introduce errors *because of* dependencies (e.g. because I used the wrong selector) and since you assume the dependencies to be fineâ¦ 2. #setUp and #tearDown are executed for every test *even if the test is a dependency*. But in my case I depend on the state that has been established by a test (so maybe I misused Phexample. Unit tests should be self contained. But then again, if they were self contained, would there be a need for dependenciesâ¦?). But that state is destroyed by #setUp and #tearDown. Then again, I *do* need to initialize and destroy some stuff sometimes (which I could to manually, I know; just saying). 3. Especially if you test things that run longer than a couple of milliseconds, the test execution time will grow very fast because of the dependencies. Every test will be run by the suite (n) + every test in a dependency chain (0 < m < inf). That amounts to roughly ~ O(n^2), which is fine for short tests but not if you have longer running tests in there So my take away message from Phexample is: itâs cool to work with and you become pretty fast. Phexample is also cool for TDD because it lets you focus on the problem at hand and everything als can just be assumed to be #given:. But: I would only recommend it for small projects / projects with low complexity (or low number of dependencies). Git has notoriously many dependencies, so I might also just be an outlier (or I may not have understood how Phexample is supposed to work). Sean, regarding your proposal, I am *not* happy with SUnit, so Iâm very happy about any ideas you have :) Cheers, Max > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/FileSystem-Git-status-update-2-tp4749696p4749970.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 20, 2014

Re: [Pharo-dev] Couchbase client

by Sven Van Caekenberghe

I am using http://www.squeaksource.com/memcached.html in Pharo On 20 Mar 2014, at 15:36, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > On Tue, Mar 18, 2014, at 07:06 PM, Esteban A. Maringolo wrote: >> I don't know the exact difference between the clients of Couchbase and >> CouchDB. >> >> I know Couchbase forked from CouchDB, and the REST API is the same. >> Hopefully the CouchDB client will work. > > It probably won't. Couchbase's protocol is basically memcache (and you > can indeed use a memcache library to talk to Couchbase in a pinch), > whereas CouchDB uses a REST protocol over HTTP. I know there used to be > at least one memcache client on Squeaksource; I'd probably see if it's > migrated to SmalltalkHub or similar. > > --Benjamin >

March 20, 2014

Re: [Pharo-dev] Class vars and inst vars of a class

by Sean P. DeNigris

Uko2 wrote > what is the difference between the class variable... pharo-users(a)lists.pharo.org is a better place to ask questions like this, so that they do not get missed amongst the dev threads, and to give the devs' inboxes a break. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Class-vars-and-inst-vars-of-a-class-tp4749910p4749998… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2014

Re: [Pharo-dev] Couchbase client

by Benjamin Pollack

On Tue, Mar 18, 2014, at 07:06 PM, Esteban A. Maringolo wrote: > I don't know the exact difference between the clients of Couchbase and > CouchDB. > > I know Couchbase forked from CouchDB, and the REST API is the same. > Hopefully the CouchDB client will work. It probably won't. Couchbase's protocol is basically memcache (and you can indeed use a memcache library to talk to Couchbase in a pinch), whereas CouchDB uses a REST protocol over HTTP. I know there used to be at least one memcache client on Squeaksource; I'd probably see if it's migrated to SmalltalkHub or similar. --Benjamin

March 20, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Sean P. DeNigris

On Mar 20, 2014, at 9:43 AM, EstebanLM [via Smalltalk] <ml-node+s1294792n4749977h75(a)n4.nabble.com> wrote: > phexample will notâ¦ be a part of the system Iâd love to standardize on a cutting edge testing framework. There have been so many great ideas (think ruby rspec) in recent times. Right now we have a chicken and egg problem... On one hand we canât express ourselves in ways that are: 1) easy to write 2) document the usage of our code i.e. easy for users to understand, and 3) reduce duplication On the other hand, we canât use libraries that help us do these things for core code. Thus, IMHO - core tests are often the poorest. My must-haves are: - mocks - phexemple-like building-on-previous-test - partial stubs - tables for input My wish list would be a real UI, taking advantage of Smalltalkâs strength, instead of leaning on the code browser and class structure, which are implementation details which constrain our thought unnecessarily. ----- Cheers, Sean -- View this message in context: http://forum.world.st/FileSystem-Git-status-update-2-tp4749696p4749982.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Esteban Lorenzano

On 20 Mar 2014, at 14:33, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Max Leske wrote >> rewriting our tests with SUnit, moving away from Phexample (for several >> reasons) > > I'm curious about those reasonsâ¦ I donât know Max reasons, but I can give you mine: FSGit based on libgit2 will be a part of the system while phexample will not, so we need sunit tests to keep it in sync with the rest of pharo :) Esteban > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/FileSystem-Git-status-update-2-tp4749696p4749970.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 20, 2014

Re: [Pharo-dev] EyeTreeInspector -> Simple Mode?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > please make sure you use the very latest image Yes, usually if you're annoyed enough to complain about something, I already complained enough to get Sven to fix it, ha ha ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/EyeTreeInspector-Simple-Mode-tp4749853p4749974.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Tudor Girba

So am I :). Doru On Thu, Mar 20, 2014 at 2:33 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Max Leske wrote > > rewriting our tests with SUnit, moving away from Phexample (for several > > reasons) > > I'm curious about those reasons... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/FileSystem-Git-status-update-2-tp4749696p4749970.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

March 20, 2014

Re: [Pharo-dev] keybindings problem?

by Tudor Girba

Thanks. Doru On Thu, Mar 20, 2014 at 2:33 PM, Andrei Chis <chisvasileandrei(a)gmail.com>wrote: > And now there is a bug report > > > https://pharo.fogbugz.com/f/cases/13102/Sequences-of-bindings-hide-individu… > > > On Thu, Mar 20, 2014 at 10:09 AM, Tudor Girba <tudor(a)tudorgirba.com>wrote: > >> We digged a bit more, and we think it's definitely a bug in Keymapping. >> >> The problem is made obvious by the global shortcuts recently introduced: >> >> https://github.com/pharo-project/pharo-core/commit/d7ff3a9a65273292a764fc8e… >> >> Some shortcuts start with Cmd+o and add something else (for example, >> Cmd+o, Cmd+s opens the settings browser). >> >> The problem is that if you only press Cmd+o, the event is swallowed and >> the Cmd+o defined locally no longer triggers. >> >> If you disable all global keybindings that start with Cmd+o: >> ((self globalCategories flatCollect: [ :each | each allEntries keymaps ]) >> select: [ :each | each shortcut beginsWith: $o command ]) do: #disable >> >> you can again use the shortcuts locally: >> ((PluggableTextMorph >> on: 'haba' >> text: #asText >> accept: nil) >> bindKeyCombination: $o command toAction: [ 'does not halt' halt ]; >> bindKeyCombination: $/ command toAction: [ 'it halts' halt ]) >> openInWorld >> >> Doru >> >> >> >> On Thu, Mar 20, 2014 at 6:54 AM, Tudor Girba <tudor(a)tudorgirba.com>wrote: >> >>> Hi, >>> >>> We (Andrei and I) are experiencing some strange behavior recently >>> related to keybindings. >>> >>> In the example below: >>> - pressing "Cmd+/" brings up the halt >>> - pressing "Cmd+o" does not bring up the halt >>> >>> ((PluggableTextMorph >>> on: 'haba' >>> text: #asText >>> accept: nil) >>> bindKeyCombination: $o command toAction: [ 'does not halt' halt ]; >>> bindKeyCombination: $/ command toAction: [ 'it halts' halt ]) >>> openInWorld >>> >>> One difference between the two is that Cmd+o is already define inside >>> the text morph, while Cmd+/ is not. However, this used to work in 30796 but >>> does not work in 30798. >>> >>> I do not have time right now to look at it more deeply. Do you know why >>> the behavior changed suddenly? What should we adapt? >>> >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

March 20, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Sean P. DeNigris

Max Leske wrote > rewriting our tests with SUnit, moving away from Phexample (for several > reasons) I'm curious about those reasons... ----- Cheers, Sean -- View this message in context: http://forum.world.st/FileSystem-Git-status-update-2-tp4749696p4749970.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2014