Hi,
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.
When you reach this point
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".
Any hep would be appreciated.
Thanks in advance, Roberto
Do not reinvent the wheel. MethodWrapper should work on Pharo else we should fix them. They should be published on SmalltalkHub Then Spy should work or another spying framework because Alex is using them.
So let us know so that we can take actions.
Stef
Hi,
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.
When you reach this point
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".
Any hep would be appreciated.
Thanks in advance, Roberto _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks Stef,
I'll look at MethodWrapper tomorrow morning! In short all I need to do is intercept a set of messages and do something (e.g., log) without touching the original implementation. I thought that Spy could have done the job, right?
Cheers, Roby
On Mar 24, 2013, at 9:44 PM, stephane ducasse stephane.ducasse@free.fr wrote:
Do not reinvent the wheel. MethodWrapper should work on Pharo else we should fix them. They should be published on SmalltalkHub Then Spy should work or another spying framework because Alex is using them.
So let us know so that we can take actions.
Stef
Hi,
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.
When you reach this point
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".
Any hep would be appreciated.
Thanks in advance, Roberto _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
The overhead occurred by MethodWrapper is higher than Spy. Spy comes with a faster implementation of the methodwrapper.
The other thing is that Spy offer ways to automatically install/uninstall the wrappers, run the unit tests and so on.
Alexandre
On Mar 24, 2013, at 4:44 PM, stephane ducasse stephane.ducasse@free.fr wrote:
Do not reinvent the wheel. MethodWrapper should work on Pharo else we should fix them. They should be published on SmalltalkHub Then Spy should work or another spying framework because Alex is using them.
So let us know so that we can take actions.
Stef
Hi,
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.
When you reach this point
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".
Any hep would be appreciated.
Thanks in advance, Roberto _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Alexandre,
Could you please help me in using your Spy tool? In a fresh Pharo 2.0 image I loaded Spy as suggested here http://www.moosetechnology.org/tools/Spy but the simple example on the webpage do not run. Any intuition?
Thanks, R
On Mar 25, 2013, at 3:55 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
The overhead occurred by MethodWrapper is higher than Spy. Spy comes with a faster implementation of the methodwrapper.
The other thing is that Spy offer ways to automatically install/uninstall the wrappers, run the unit tests and so on.
Alexandre
On Mar 24, 2013, at 4:44 PM, stephane ducasse stephane.ducasse@free.fr wrote:
Do not reinvent the wheel. MethodWrapper should work on Pharo else we should fix them. They should be published on SmalltalkHub Then Spy should work or another spying framework because Alex is using them.
So let us know so that we can take actions.
Stef
Hi,
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.
When you reach this point
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".
Any hep would be appreciated.
Thanks in advance, Roberto _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
[EDIT] I've just seen you updated the page! Now I'll try the updated example!
On Mar 25, 2013, at 1:33 PM, "roberto.minelli@usi.ch" roberto.minelli@usi.ch wrote:
Hi Alexandre,
Could you please help me in using your Spy tool? In a fresh Pharo 2.0 image I loaded Spy as suggested here http://www.moosetechnology.org/tools/Spy but the simple example on the webpage do not run. Any intuition?
Thanks, R
On Mar 25, 2013, at 3:55 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
The overhead occurred by MethodWrapper is higher than Spy. Spy comes with a faster implementation of the methodwrapper.
The other thing is that Spy offer ways to automatically install/uninstall the wrappers, run the unit tests and so on.
Alexandre
On Mar 24, 2013, at 4:44 PM, stephane ducasse stephane.ducasse@free.fr wrote:
Do not reinvent the wheel. MethodWrapper should work on Pharo else we should fix them. They should be published on SmalltalkHub Then Spy should work or another spying framework because Alex is using them.
So let us know so that we can take actions.
Stef
Hi,
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.
When you reach this point
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".
Any hep would be appreciated.
Thanks in advance, Roberto _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
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@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!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Sorry Roby,
It should be: DemoTestCoverageMethodSpy>>beforeRun: methodName with: listOfArguments in: receiver nbOfExecutions := nbOfExecutions + 1. testMethodsThatRunMe add: self profiler class currentTestMethod
(this is not really elegant, I agree)
Cheers, Alexandre
On Mar 25, 2013, at 4:25 PM, roberto.minelli@usi.ch wrote:
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@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!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I think Frederic Pluquet has worked on that on some point.
Cheers, Alexandre
On Mar 25, 2013, at 1:41 PM, Ben Coman btc@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!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Did you migrate Spy on SmalltalkHub? Do you need a CI job to run the tests of Spy automatically? Do you have a configurationOfSpy?
For MethodWrappers do you have a working version somewhere? Because I would like to publish them on SMalltalkhub :)
Hi!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Give me a few days to carefully answer. Tomorrow we have a big big deadline
Alexandre
On Mar 27, 2013, at 3:09 AM, stephane ducasse stephane.ducasse@free.fr wrote:
Did you migrate Spy on SmalltalkHub? Do you need a CI job to run the tests of Spy automatically? Do you have a configurationOfSpy?
For MethodWrappers do you have a working version somewhere? Because I would like to publish them on SMalltalkhub :)
Hi!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Spy is now on SmalltalkHub
Alexandre
On Mar 27, 2013, at 3:09 AM, stephane ducasse stephane.ducasse@free.fr wrote:
Did you migrate Spy on SmalltalkHub? Do you need a CI job to run the tests of Spy automatically? Do you have a configurationOfSpy?
For MethodWrappers do you have a working version somewhere? Because I would like to publish them on SMalltalkhub :)
Hi!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Apr 4, 2013, at 6:28 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
Spy is now on SmalltalkHub
cool do you have a test group? Because we could add it to the ci
Stef
Alexandre
On Mar 27, 2013, at 3:09 AM, stephane ducasse stephane.ducasse@free.fr wrote:
Did you migrate Spy on SmalltalkHub? Do you need a CI job to run the tests of Spy automatically? Do you have a configurationOfSpy?
For MethodWrappers do you have a working version somewhere? Because I would like to publish them on SMalltalkhub :)
Hi!
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 can simply invoke it with:
| packageSpy | packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
You need to define 4 classes, as indicated in the webpage.
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
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Ben Coman -
roberto.minelli＠usi.ch -
stephane ducasse