February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Obsolete classes after tests

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.1.2-DevImage Comment #10 on issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Obsolete classes after tests http://code.google.com/p/pharo/issues/detail?id=3575 in 11421

Feb. 27, 2011

[Pharo-project] [update 1.2] #12339

by Marcus Denker

12339 ----- Issue 3575: [Failing Tests] Obsolete classes after tests (workaround) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 27, 2011

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Obsolete classes after tests

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2-DevImage Comment #9 on issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Obsolete classes after tests http://code.google.com/p/pharo/issues/detail?id=3575 in 12339

Feb. 27, 2011

Re: [Pharo-project] Issue 3620 in pharo: Settings: OCompletion settings appear twice

by pharo＠googlecode.com

Updates: Status: Accepted Comment #11 on issue 3620 by marcus.d...(a)gmail.com: Settings: OCompletion settings appear twice http://code.google.com/p/pharo/issues/detail?id=3620 So what is the *simplest* *easiest* workaround for this so that we can actually release 1.2?

Feb. 27, 2011

Re: [Pharo-project] Issue 3484 in pharo: Windows VM in One click image for 1.2 not yet customized

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3645 Comment #7 on issue 3484 by marcus.d...(a)gmail.com: Windows VM in One click image for 1.2 not yet customized http://code.google.com/p/pharo/issues/detail?id=3484 (No comment was entered for this change.)

Feb. 27, 2011

Re: [Pharo-project] Issue 3645 in pharo: Update Hudson One-Click build files for 1.2

by pharo＠googlecode.com

Updates: Cc: marcus.denker stephane.ducasse Comment #3 on issue 3645 by marcus.d...(a)gmail.com: Update Hudson One-Click build files for 1.2 http://code.google.com/p/pharo/issues/detail?id=3645 Issue 3484 has been merged into this issue.

Feb. 27, 2011

Re: [Pharo-project] Good reference on time on unit testing?

by Schwab,Wilhelm K

Understood. But, doing it correctly, how much of your time do you spend on the test writing/maintenance side? I found some blog posts, but I was hoping for some peer-reviewed papers that go on the record. I am trying to make the point you are making, and it will go over better if I can point to literature and some numbers that I suspect will be seen as sobering. Tests ARE being "written after" in this case, but assuming they change to a proper process, they still need to understand that tests take thought and work. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Peter Hugosson-Miller [oldmanlink(a)gmail.com] Sent: Sunday, February 27, 2011 2:58 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Good reference on time on unit testing? +100 Couldn't have said it better myself! -- Cheers, Peter. On 27 feb 2011, at 08:27, laurent laffont <laurent.laffont(a)gmail.com<mailto:laurent.laffont@gmail.com>> wrote: On Sun, Feb 27, 2011 at 4:52 AM, Schwab,Wilhelm K <<mailto:bschwab@anest.ufl.edu>bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Hello all, Can anyone recommend a good reference on the amount of time one should expect to spend writing tests? I will have to be the messenger (will be wearing running shoes just in case...), but I want the message to come from a solid source. If you develop the TDD way (which I always do at work) then I would say this question is not valid. Your production code will be there because of tests. In legacy system, new and refactored code will be there because of tests. IMHO the questions "how much time should I spend writing tests?" or "how many tests should I write ?" are raised when tests are written after. And sadly tests often become a burden in this case and doesn't support the pressure of releases / last minute changes / ... (I've done it this way almost 10 years ago, not good :) In TDD the question is "which stories / scenarios do we have to implement ?". It's more a Product owner / customer point of view. The best book on TDD I've read is Dave Astels TDD: a practical guide (Indeed, this one has really changed my mind on how testing should be done, and other books I've read since don't). Laurent Bill

Feb. 27, 2011

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Obsolete classes after tests

by pharo＠googlecode.com

Comment #8 on issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Obsolete classes after tests http://code.google.com/p/pharo/issues/detail?id=3575 As this just happens after running all tests, I propose to remove the Obselete classes test in 1.1 and 1.2 and move the problem to be fixed in 1.3 (the tests are messy wrt. to changes to the system anyway, packages are dirty, files are written...)

Feb. 27, 2011

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #15 on issue 3707 by marcus.d...(a)gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 (No comment was entered for this change.)

Feb. 27, 2011

Re: [Pharo-project] Issue 3732 in pharo: default omni browser size bigger

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3732 by marcus.d...(a)gmail.com: default omni browser size bigger http://code.google.com/p/pharo/issues/detail?id=3732 fix attached. This just makes the window minmally as big as the standard browser Attachments: OBBrowser-initialExtent.st 243 bytes

Feb. 27, 2011