Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Enable monitoring of objects during and after test runs
Options
Previous Topic Next Topic
larsbeck
#1 Posted : Friday, August 17, 2012 8:39:11 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/17/2012(UTC)
Posts: 1
Location: Germany
Hi,

first of all I want to say thanks for this great tool! It makes development and testing so much easier!

The feature I would love to see would allow me to decorate some of the objects involved in my tests with a new attribute, so that I can always see their properties during/at the end of a test run.

This request is motivated by this talk: http://vimeo.com/36579366#t=1156 where Bret Victor says that
Quote:
creators need an immediate connection to what they create
- and I agree with him. At the timestamp in the link he shows a development environment which allows the dev to immediately see what his code does (in his example he develops a binary search algorithm - he has many more examples, which make it even easier to see the benefits). With NCrunch it should be possible to get something similar. We could have a "Monitoring window", which shows all objects which are decorated with an "NCrunchMonitoringAttribute" and their properties during and at the end of a test run.

If NCrunch has a plugin system (I didn't find one), I would be willing to contribute this feature as a plugin.

Best,

Lars
Back to top
WWW
Remco
#2 Posted : Saturday, August 18, 2012 12:06:03 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,140

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Lars,

Thanks for posting and for sharing this suggestion. I have been considering for some time ways in which NCrunch can capture more information during test runs, as it would be extremely useful to be able to somehow show this information inline in the IDE while you work. It would be yet another thing that would help to draw people away from needing to fire up a debugger in order to inspect the workings of their code.

The challenges around capturing runtime information are always around dealing with vast amounts of data and finding ways of sifting this down to the information that's actually relevant. NCrunch's approach around collecting performance and coverage data has been fairly clear-cut, though it's harder to make this work for properties on an object.

The use of an attribute is a good idea. I'll have a bit more of a think about this and see what other options there may be, and what may be possible. Thanks for taking the time to suggest this.


Cheers,

Remco
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.036 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download