Including Diagnostic Trace Data with Bugs that are Difficult to Reproduce
You can collect specific diagnostic trace information when you run your tests to help isolate bugs that are difficult to reproduce. This information enables you to use IntelliTrace to trace through what really occurred in your application to cause the bug.
Note
IntelliTrace can only be used with applications that are written with managed code.
Collecting IntelliTrace information reduces the amount of time it takes to reproduce and diagnose an error in an application's code. When a test step fails and a bug is filed, an IntelliTrace file with an extension of .iTrace is automatically linked to the bug and is available together with the test results. The IntelliTrace file can then be used by another individual who can replicate your local test session on their computer without having to reproduce the bug directly. This reduces the probability of a bug being resolved as non-reproducible because you no longer have to reproduce the problem to debug the scenario. For more information, see Debugging Code Faster by Reviewing its History with IntelliTrace.
Using IntelliTrace data attached to bugs to help isolate non-reproducible bugs
.png "Diagnostic trace data attached to bugs")
Key Tasks
Tasks |
Associated Topics |
|---|---|
Configure a test setting to collect diagnostic trace data: You can configure a test setting that is applied to a test plan. The test plan contains tests that you want to include as well as the IntelliTrace information to collect. |
|
Submitting bugs with diagnostic trace data attached: If you have enabled IntelliTrace using a test setting, you can create a bug during a test and include the IntelliTrace file for other team members to use to debug the issue. |