Add trace script to MSpec
Reported by Brian Ford | May 6th, 2008 @ 11:54 AM | in 1.0 preview
Enhance Evan's basic trace script to generate the correct profile filter format for MSpec from running a target application.
Comments and changes to this ticket
-
Evan Phoenix May 8th, 2008 @ 04:49 PM
- → Assigned user changed from Brian Ford to Ryan Davis
Easier would be to modify the stdlib tracer.rb to dump out the properly data and then format it into yaml. See spec/profiles for examples of current profiles.
-
Brian Ford May 8th, 2008 @ 06:01 PM
This is hopefully obvious, but the format of the profile yaml files is a hash of arrays where the hash keys are
Class#for instance methods andClass.for class/module methods, and each key's value is a list of corresponding methods. The existing files under spec/profiles were generated by hand from a trace provided by John Lam (except core.yaml which was generated by mspec/lib/mspec/utils/name_map.rb output to yaml). -
Ryan Davis May 15th, 2008 @ 07:08 PM
- → State changed from new to open
- → Assigned user changed from Ryan Davis to Brian Ford
Added tools/tracer.rb. Poke at it.
How do you want it added to mspec? I don't get that part.
If that was all I was supposed to do, then cool... assign back, and I'll close after I'm done polishing.
If not, reopen and add notes as to what you'd like.
-
Ryan Davis May 15th, 2008 @ 07:11 PM
- → State changed from open to resolved
- → Assigned user changed from Brian Ford to Ryan Davis
done
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
