Historical Debugger and Test Impact Analysis in Visual Studio Team System 2010
- Posted: Oct 02, 2008 at 11:26 AM
- 39,825 Views
- 19 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- WMV (WMV Video)
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Are you tired of constantly setting breakpoints to hone in on a pesky bug? How would you like to be able to step "back in time" through your debugger? The Historical Debugger in Visual Studio Team System 2010 promises to revolutionize your debugging experience.
Habib Heydarian takes us through a demonstration of just a few of its capabilities.
But wait... there's more! Habib also shows us the new Test Impact Analysis feature his team is working on. With Test Impact Analysis it's possible to determine which of your tests will be... well... impacted by the code changes you're making! Not only does this mean that your unit test suite can run more quickly, but it can also lead to better testing and fewer bugs in software projects.
This "Humanized Screencast" is best viewed at fullscreen using the high-quality WMV download.
But wait... there's more! Habib also shows us the new Test Impact Analysis feature his team is working on. With Test Impact Analysis it's possible to determine which of your tests will be... well... impacted by the code changes you're making! Not only does this mean that your unit test suite can run more quickly, but it can also lead to better testing and fewer bugs in software projects.
This "Humanized Screencast" is best viewed at fullscreen using the high-quality WMV download.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Great demo. So when can we get the CTP bits????
Bob Hanson
Brian Harry has said "soon" on his blog. Beyond that, of course, we're going to keep you guessing.
Blind feedback: Before watching the video (dinner first), I want my 3rd party .Net language to be able to create historical snapshots (or whatever they're called). For example, traditionally, programmer errors would occur before and after file open statements or when spawning processes. Can my runtime tell the debugger to create a snapshot and name it? How will histroical debugging be exposed for 3rd party languages?
It would be great if it could be hooked up to a running production application so we don't have to capture dumps.
John
We are working towards having a solution where you don't need VS installed to be able to collect a log file for the Historical Debugger. We haven't finalized a plan yet, so I can't go into detail about what the final experience will be.
Thanks,
HabibH.
In VS 2010, the Historical Debugger feature will work for C++/CLI, but not for native C++. This was a really difficult decision for us but we are thinking hard about how to address this in the future.
Thanks,
HabibH.
This seems to be only available for VSTS developers.... or am I just not seeing it? Is there a plan to push this out to all us poor development shops who aren't on VSTS? I'm dieing to use this feature!!
Microsoft needs to provide support for this feature in the Professional Version of Studio.
This is an idea whose time has come. I believe that this kind of things will replace logging. Logging clutters up code, slows down performance always (even if to see if it's turned on), and even when used copiously never seems to actually capture the state that's needed. Recorded debugging is the future! Mu ha ha ha
Now about VS 2010's feature. What I've seen so far seems to indicated that the user can't place their own "diagnostic events" (breakpoints) anywhere they need. Without this, the feature suffers from the same problem as logging... the capture points are arbitrary. I would like to set a bunch of breakpoints, each with a set of watches (expecially with expressions like I can normally), then be able to send this capture data to any location running my code (e.g. live running apps), capture the data, then send it back and walk through it in the IDE. It would be one of the biggest advances in programmer productivity in years!
Best,
--
Nathan Allan
Database Consulting Group
Looking forward for native C++ support!
Hi there,
we are only working with native code (C++).
When will these features (historical debugging, code analysis, impact tests) be available for C++ developers?
Thanks,
Andi
Remove this comment
Remove this thread
close