[COTDC] 47 - TAssertable

Today: TAssertable Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

[COTDC] 47 - TAssertable

On Tue, Apr 12, 2011 at 10:14 PM, laurent laffont <laurent.laffont@... > wrote: > Today: TAssertable > Is it used ? Could not find any reference. Laurent. > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected...

[COTDC] 47 - TAssertable

... Kuhn introduce it. Check http://forum.world.st/template/NamlServlet.jtp?macro=search_page&node=1294837&query=TAssertable Cheers Mariano > > Laurent. > > > > >> >> Comment Of The Day Contest - One Day One Comment >> Rules: >> #1: Each day a not commented class is elected. Each day...

[COTDC] 47 - TAssertable

... those > methods, but it is not the case. Even more, TAssertable users size -> 0. > > So...seems a work half done. Adrian Kuhn introduce it. Check > > http://forum.world.st/template/NamlServlet.jtp?macro=search_page&node=1294837&query=TAssertable > > OK I put your answer as comment...

TAssertable isBehavior -> false

shouldn't TraitBehavior implement isBehavior ^true ? Or maybe put that method in TPureBehavior Guille

[update 1.1] #11325

11325 ----- - Added TAssertable Stef _______________________________________________ Pharo-project mailing list Pharo-project@... http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Issue 3246 in pharo: Duplicated code on SUnit

Status: Accepted Owner: estebanlm New issue 3246 by estebanlm: Duplicated code on SUnit http://code.google.com/p/pharo/issues/detail?id=3246 Pharo image: core Pharo core version: 1.2 SUnit class TestCase and trait TAssertable have duplicated code, and also TAssertable is not used anywhere. It should be only one!

[update 1.3] #13158

... - L.Laffont 46 - SUnitUnloader - S.V.Caekenberghe 47 - TAssertable - M.M.Peck 48 - ClassFactoryForTestCase - A.Bergel Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

[update 2.0] #20313

20313 ----- Issue 6745: Failing tests related to Zinc http://code.google.com/p/pharo/issues/detail?id=6745 Issue 6052: would be good that TestAsserter uses TAssertable http://code.google.com/p/pharo/issues/detail?id=6052 -- Marcus Denker -- http://marcusdenker.de

Does somebody use resumable test failures?

We have a set of methods like #assert:description:resumable: That - have no users besides the tests that test the feature (no real tests using it) - there are two implementations and the one in TAssertable is broken (sends #isResumable: that has no implementors) Does somebody see some value in this method? https://pharo.fogbugz.com/f/cases/16373/Methods-called-but-not-implemented-in-SUnit Guille

Deadlock detection for testcases

... > [ super runCase ] > valueWithin: self expectedMaxRuntime > onTimeout: [ self failWithTimeout ] +1, being able to debug your tests is a must have. Please note that is also TAssertable >> #should:notTakeMoreThan: TAssertable >> #should:notTakeMoreThanMilliseconds...

[update 1.3] #13158

... > 42 - ExpanderMorphContracted - G.Chambers > 43 - FreeTypeFontSelectorDialogWindow - L.Laffont > 44 - ColorChanged - L.Laffont > 45 - TestCoverage - L.Laffont > 46 - SUnitUnloader - S.V.Caekenberghe > 47 - TAssertable - M.M.Peck > 48 - ClassFactoryForTestCase - A.Bergel > > Laurent Laffont...