Indeed TestCase is a really a special class and it can be really looking strange at first.
On Sun, Apr 22, 2018 at 2:20 PM, Sean P. DeNigris <s...@clipperadams.com> wrote: > Gregg Williams wrote >> Hi—I’m a beginner in Pharo and am working my way through Pharo by Example >> 5.0 (PbE) and Learning OOP and TDD with Pharo (LOTWP). > > Welcome! That's a great way to start :) > > > Gregg Williams wrote >> 1) These two methods are defined on the instance side (the Class button is >> *not* selected). If so, what is the receiver when they are used? > > I think the other two replies covered this and your other questions > technically, but I just want to mention that the TestCase class can be a bit > confusing. It represents a convenient way to deal with tests in a class > browser, at the expense of being the most understandable OOP design. Suffice > it to say that whenever a test is run, SUnit, the testing system, will do > the magic to create an instance of your TestCase subclass. This is what > happens when you click the test bubble in the browser, and this instance is > what `self` refers to in tests. HTH > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >
