Hi, So this is not problem of Spy2, but a bug of Hapao. There should be no problem instrumenting String with Spy2 if your profiler is correct, the proof of this is that the image does not explode when you were debugging the execution (I was actually able to open a browser and check the tests of String).
This problem happened because we naively assumed, at least in this implementation Hapao, that for every Test Object there is a Test Method associated in the class of the Test Object. This is not correct for inherited tests, where the Test Method is in one of the superclasses. I will submit a fix for that as soon as possible ;) Thanks for the bug report!! Alejandro > On Jan 19, 2016, at 8:58 AM, stepharo <[email protected]> wrote: > > Hi sheridan > > spy string can be a challenge. > Now I was thikning recently that we should have tests for Ring. So if you are > interested I would love to review your tests. > > Sef > > > Le 18/1/16 22:45, [email protected] a écrit : >> Hi there, >> >> I am trying to use Hapao to check test coverage in the String class and have >> run across some trouble. To begin, I loaded Spy2 and Roassal2 using the >> following code: >> >> Gofer new smalltalkhubUser: 'ObjectProfile' >> project: 'Roassal2'; >> package: 'ConfigurationOfRoassal2'; >> load. >> (Smalltalk at: #ConfigurationOfRoassal2) load. >> >> Gofer it >> smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; >> configurationOf: 'Spy2'; >> loadStable. >> >> Hapao then showed up in the "World" menu, and I selected it. I chose "Hapao >> @ class ... " and entered "String". >> >> Hapao starts running tests, but before long a debugger comes up with the >> error: KeyNotFound: key #testClassComment not found in MethodDictionary . >> IF I click "Proceed", other keyNotFound errors come up. This is in a 50524 >> image. >> >> Is there something wrong with the way I am invoking Hapao? >> Many thanks, >> Sheridan >> >> >> > >
