25 Mar
2013
25 Mar
'13
9:25 p.m.
Hi Alexandre,
Thanks for updating the webpage.
Btw I've been trying the new code but I got a MNU on DemoTestCoverageMethodSpy
class>>currentTestMethod which comes from
DemoTestCoverageMethodSpy>>beforeRun:with:in:.
I think it has still something to do with the new code involving the Profiler class. Do
you have a quick solution for that?
Thanks in advance,
Roby
On Mar 25, 2013, at 6:41 PM, Ben Coman <btc(a)openInWorld.com> wrote:
Looks very interesting. What would be cool would be
building a Message Sequence Chart [1] using Mondrian for model interactions.
For example, given a model root, Spy on all subclass methods, then from workspace invoke
a starting method from which to trace.
Or, more advanced, be able to invoke this from the debugger.
cheers -ben
[1] http://en.wikipedia.org/wiki/Message_Sequence_Chart
Alexandre Bergel wrote:
Hi!
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev I'm was exploring some methods to build
method wrappers and I discovered Spy.
Unfortunately the sample code provided on
http://www.moosetechnology.org/tools/Spy
does not run.
I have updated the webpage. It was a bit desynchronized with the actual code.
You may want to have a look at
http://bergel.eu/download/papers/Berg10f-Spy.pdf
This is a longer description of the framework
When you reach this point
You need to define 4 classes, as indicated in the webpage.
You can simply invoke it with:
| packageSpy |
packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed:
'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
Afterward this class is defined but still there
is no message "runTestAndGatherForPackageNamed".
use instead:
runTestsForPackagesMatching: 'YourPackages*'
Let us know if you still experience problems.
Cheers,
Alexandre