Shai Raiten's Blog : Data Collectors

Test Attachment Cleaner

shair — Thu, 09 Dec 2010 20:34:20 GMT

Test Attachment Cleaner

Overview:

In Visual Studio 2010, with the introduction of Visual Studio Test Professional 2010 & Visual Studio Premium/Ultimate 2010 SKUs, testers can author manual and automated Test cases, configure the different diagnostic data collectors (as part of Test Settings), associate the Test Settings with Test Plan/Suites and then execute these test cases as part of Test Runs. The execution of a Test Run (whether automated or manual) generates a bunch of diagnostic data, which may be captured either automatically by the system or manually by the tester. This diagnostic data is critical in eliminating the “no repro” bug scenarios between the testers and developers.

However, the downside of this rich diagnostic data captures is that the system/user generated diagnostic data, over a period of time, can grow at a rapid pace and start taking up database space. With Visual Studio 2010, the database administrator has little or no control over what data gets attached as part of Test Runs – i.e., there are no policy settings he can control to limit the size of the data capture OR no retention policy to determine how long to hold this data before initiating a cleanup. In such scenarios, the Admin has no mechanism to:

1. Determine which set of diagnostic captures is taking up how much space AND

2. Reclaim the space for runs which are no longer relevant from business perspective.

The “Test Attachment Cleaner” powertool fills this void by serving both the above points.

Usage:

The Test Attachment Cleaner is a command line powertool (tcmpt.exe attachmentcleanup), which accepts the following parameters:

Tcmpt.exe attachmentcleanup

/collection: TeamProjectCollectionUrl

/project: TeamProject

/settings: SettingsFilePath

[/out: ReportFilePath]

[/mode: Preview/Delete]

Sample Setting files for core scenarios: As part of the package, sample setting files are provided which cater to the following 5 core scenarios. The readme document contains additional details around the different knobs used within the sample setting files.

Scenario#1: Identify list of attachments taking up database space of more than 1 GB per attachment
Scenario#2: View/Delete IntelliTrace log files over a size of 500 MB
Scenario#3: View/Delete all Video log files with Test run creation date older than specific date with no active bugs
Scenario#4: View/Delete all TRX & COV log files for test runs that happened between 30 and 90 days in age & do not perform the Linked Bugs lookup query
Scenario#5: View/Delete all custom/user attachments over size of 5 MB with no active or resolved bugs on test runs between 2 dates

Download Test Attachment Cleaner

Teched 2010 - Applied Software Testing with Visual Studio 2010 – Done

shair — Tue, 30 Nov 2010 14:30:12 GMT

Teched 2010 - Applied Software Testing with Visual Studio 2010 – Done

I’ll start saying – Thanks everyone who participate at my lecture in Teched Israel 2010, I’ll also like to say thanks to Tzvia Gitlin Troyna the ALM sessions manager and to Sela Group for helping and supporting me during that period.

My Session was loaded with Information regarding Automated/Manual Testing in Visual Studio 2010 & Microsoft Test Manager and there is not doubt that the Testing Space in Visual Studio 2010 is the future of Automated/Manual Testing.
During my session I had A LOT of questions and not enough time to answer all those questions, so as promised I’m writing this post to give you the guidelines based on my presentation topics in order to help get started with Test Automation using Visual Studio 2010 and Microsoft Test Manager.

Microsoft Test Manager – More Info
- Fast Forward Automation – We saw how from manual Test Case you can create a simple automatic test without writing code.
- Rich Bugs – Using Data Collectors we saw how easy is to open bug with all the information you need.
Web Testing
We saw how to record Web Site or Desktop application HTTP/S request and rerun those request with different parameters from external data source. – More Info - Screencasts
Load Testing
You can Do It!!! we saw how easy create new load testing can be using Visual Studio 2010 – More Info
Coded UI Testing – More Info
- From Existing Test Case – When the “Manual Tester” working on his Test Cases as an Automation Guy or Developer I can generate the Coded UI from the Manual Test Case. (Fast Forward Automation).
- New – Create a powerful UI Automation using Coded UI Test Builder.

Any other question feel free to contact me – shair[at]sela.co.il

Download Teched Presentation

Thanks again and Enjoy

Tech-Ed 2010 – Applied Software Testing with Visual Studio 2010 – All In One

shair — Tue, 09 Nov 2010 16:29:00 GMT

Tech-Ed 2010 – Applied Software Testing with Visual Studio 2010 – All In One

Teched Israel 2010 is going to happen next month in Eilat between the 28-30 of November.

On this Teched I’ll have the pleasure to present a session about Applied Software Testing with Visual Studio 2010

In this session I’ll demonstrate how to use the following:

Microsoft Test Manager – Fast Forward Automation
Web Performance Testing
Load Testing
Coded UI Testing

Why? So YOU can do Automatic and Load Testing by yourself!!!

This is All In One session and if you want to know more about Testing in Visual Studio 2010 you should be there!

http://www.microsoft.com/israel/TechEd2010/Tracks/ALM.aspx

More Lectures I’ll recommend you to go: (Sela Collage Speakers)

Microsoft Key Note At SIGIST 2010 - Test Automation - Done

shair — Wed, 16 Jun 2010 23:24:00 GMT

Microsoft Key Note At SIGIST 2010 - Test Automation – Done

Today I had the honor to participate at SIGIST 2010 conference (The third year) and be a part of Microsoft Key Note on Test Automation in Visual Studio

2010 and Microsoft Test Manager. (Last year lecture - Sigist 2009 – Lab Management & Pictures)

I’ve showed couple of cool demos using “Fast-Forward for Manual Testing”, Rich Bugs using Data Collectors and Lab Manager solution.

And I showed a short demo on how to use Eclipse IDE with TFS 2010 using Team Explorer Everywhere (Heterogeneous).

I got great feedbacks from people attending and I’ll would like to thank you all and hope to see you next year!

How To Create Custom DataCollector In Visual Studio 2010 – Part 2

shair — Mon, 19 Apr 2010 13:52:54 GMT

How To Create Custom DataCollector In Visual Studio 2010 – Part 2

In the previous post (How To Create Custom DataCollector In Visual Studio 2010 – Part 1)I showed how to create a Custom Data Collector using Visual Studio 2010, Here we continue improving our Data Collector using external Xml Configuration files.

Instead of add hardcoded values into your code use the Xml to take and save user settings.

Download Demo Project

Step 1 – Add Configuration File

To collect a log file when a test finishes based on what the user configured in test settings, you must create an App.config file and add it to your solution

Copy below format into the app config file:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="DataCollectorConfiguration"
      type="Microsoft.VisualStudio.TestTools.Execution.DataCollectorConfigurationSection, 
      Microsoft.VisualStudio.QualityTools.ExecutionCommon, 
      Version=4.0.0.0, Culture=neutral, 
      PublicKeyToken=b03f5f7f11d50a3a" />
  </configSections>
  <DataCollectorConfiguration xmlns="http://microsoft.com/schemas/VisualStudio/TeamTest/2010">
    <DataCollector typeUri="datacollector://ShaiRaiten/LocalLogsCollector/1.0">
      <DefaultConfiguration>
        <Folder Path="C:\Logs\"/>
        <Folder Path="C:\Logs2\"/>
      </DefaultConfiguration>
    </DataCollector>
  </DataCollectorConfiguration>
</configuration>
 

Make sure the DataCollector typeUri attribute is the same as [DataCollectorTypeUri("datacollector://ShaiRaiten/LocalLogsCollector/1.0")] from the Data Adapter class.

Step 2 – Initialize Configuration Element

In the Initialize method make sure to Initialize the Configuration XmlElement .

private XmlElement configurationSettings;

public override void Initialize(XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink sink,
DataCollectionLogger logger, DataCollectionEnvironmentContext environmentContext)
{
    configurationSettings = configurationElement;
    events.SessionEnd += new EventHandler<SessionEndEventArgs>(events_SessionEnd);
}

Step 3 – Use Configuration Element

 
void events_SessionEnd(object sender, SessionEndEventArgs e)
{
    // Get any files to be collected that are
    // configured in your test settings
    List<string> files = getFilesToCollect(e.Context);
 
    // For each of the files, send the file to the data sink
    // which will attach it to the test results or to a bug
    foreach (string file in files)
    {
        dataSink.SendFileAsync(e.Context, file, false);
    }
 
}
 
// A private method that returns the file names
private List<string> getFilesToCollect(DataCollectionContext context)
{
    XmlNodeList folders = configurationSettings.GetElementsByTagName("Folder");
 
    // Build the list of folder to collect from the 
    // "Path" attributes of the "Folder" nodes.
    List<string> result = new List<string>();
    foreach (XmlNode folder in folders)
    {
        XmlAttribute pathAttribute = folder.Attributes["Path"];
        if (pathAttribute != null && !String.IsNullOrEmpty(pathAttribute.Value))
        {
            if (Directory.Exists(pathAttribute.Value))
            {
                string[] files = Directory.GetFiles(pathAttribute.Value);
                foreach (string file in files)
                    result.Add(file);
            }
        }
    }
    return result;
}

Download Demo Project

How To Create Custom DataCollector In Visual Studio 2010 – Part 1

shair — Mon, 19 Apr 2010 13:51:01 GMT

How To Create Custom DataCollector In Visual Studio 2010 – Part 1

What is DataCollector - Team System 2010 Beta 2 – Diagnostic Data Adapters – No More No Repro!

If you remember I’ve already wrote on how to create a custom data collector:

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 1, VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 2

but between Beta 2 and RTM there were couple of changes with Data Collectors.

Download Demo Project

Step 1 – Getting Started

Create a Class library project and add two references:

   Microsoft.VisualStudio.QualityTools.Common 
Microsoft.VisualStudio.QualityTools.ExecutionCommon.dll 
 

You can find those assemblies C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0
(If you are not using 64bit operation system - C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\ReferenceAssemblies\v2.0

Step 2 – Create Data Collector Class

1. Add new class to your project with the Data Collector name, make sure the class defined as Public and add both using to the class:

using Microsoft.VisualStudio.TestTools.Execution;

using Microsoft.VisualStudio.TestTools.Common;

2. Add the Data Collector attributes

[DataCollectorTypeUri("datacollector://ShaiRaiten/LocalLogsCollector/1.0")]
[DataCollectorFriendlyName("Local Logs Collector")]

3. Add DataCollector interface and implement it. (Beta 2 – IDataCollector)
This is what you should see:

 
public override void Initialize(XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink sink,
DataCollectionLogger logger, DataCollectionEnvironmentContext environmentContext)
{
}

Step 3 – Implement Custom Data Adapter

Using the DataCollectionEvents add the desire events for the Custom Data Adapter.

CustomNotification      Raised when a custom notification occurs.
DataRequest                Raised to request intermediate data.
SessionEnd                   Raised when a test session ends.
SessionPause                Raised when a test session pauses.
SessionResume            Raised when a test session resumes.
SessionStart                 Raised when a test session starts.
TestCaseEnd                Raised when a test case ends.
TestCasePause             Raised when a test case pauses.
TestCaseReset             Raised when a test case resets.
TestCaseResume         Raised when a test case resumes.
TestCaseStart              Raised when a test case starts.
TestStepEnd                Raised when a test step ends.
TestStepStart              Raised when a test step starts.

And define DataCollectionSink for storing files as attachments.

For Example:

private DataCollectionEvents dataEvents;
private DataCollectionLogger dataLogger;
private DataCollectionSink dataSink;
 
public override void Initialize(XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink sink,
DataCollectionLogger logger, DataCollectionEnvironmentContext environmentContext)
{
    dataEvents = events;  // The test events
    dataLogger = logger;  // The error and warning log
    dataSink = sink;      // Saves collected data
    // Configuration from the test settings
 
    events.SessionEnd += new EventHandler<SessionEndEventArgs>(events_SessionEnd);
}

Now write the code to collect the logs from the specified folder.

void events_SessionEnd(object sender, SessionEndEventArgs e)
{
    string LogPath = @"C:\Logs";
    try
    {
        if (Directory.Exists(LogPath))
        {
            string[] files = Directory.GetFiles(LogPath);
            foreach (string f in files)
            {
                dataSink.SendFileAsync(e.Context, f, false);
            }
        }
    }
 
    catch (Exception ex)
    { throw ex; }
}

Download Demo Project

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 2

shair — Sun, 17 Jan 2010 16:58:50 GMT

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 2

In my previous post Diagnostic Data Adapters – Create Custom Adapter – Part 1 I’ve showed how to create a Custom Data Adapter, this post will be on how to add a Configuration File to your Custom Data Adapter.

Download Demo Project

Step 1 – Add Configuration File

In your Data Adapter project add a new xml file and change the name to <name of your data diagnostic adapter>.dll.config

Copy below format into the xml config file:

<?xml version="1.0" encoding="utf-8"?>
<Config>
<DataCollector typeUri="datacollector://ShaiRaiten/LogsCollector/1.0" enabledOnCollectionOnlyAgents="true">
    <DefaultConfiguration>
      <Folder FullPath="C:\Logs\Day"/>
      <Folder FullPath="C:\Logs\Night"/>
    </DefaultConfiguration>
</DataCollector>
</Config>

 
Make sure the DataCollector typeUri attribute is the same as [DataCollectorTypeUri("datacollector://ShaiRaiten/LogsCollector/1.0")] from the Data Adapter class.

Step 2 – Initialize Configuration Element

In the Initialize method make sure to Initialize the Configuration XmlElement.

private XmlElement config;
 
public void Initialize(System.Xml.XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink dataSink, DataCollectionLogger logger, AgentContext agentContext)
{
    this.config = configurationElement;
 
    Events.TestCaseEnd += new EventHandler<TestCaseEndEventArgs>(Events_TestCaseEnd);
}

Step 3 – Use Configuration Element

void Events_TestCaseEnd(object sender, TestCaseEndEventArgs e)
{
    try
    {
        List<string> folders = new List<string>();
        XmlNode currentNode = config.FirstChild;
 
        while (currentNode != null)
        {
            if ((currentNode.Name == "Folder") && (currentNode.Attributes["FullPath"] != null))
                folders.Add(currentNode.Attributes["FullPath"].Value);
            currentNode = currentNode.NextSibling;
        }
 
        foreach (string folder in folders)
        {
            string[] files = Directory.GetFiles(folder);
            foreach(string file in files)
                dataSink.SendFileAsync(e.Context, file, false);
        }
    }
    catch (Exception ex)
    { throw ex; }
}

Step 4 – Install Configuration File

End you’re almost done, Build the solution, and then copy the built assembly and the Configuration file to -
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\DataCollectors

Now, Run the test and see the results below:

Full Code :

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.VisualStudio.TestTools.Execution;
using System.Xml;
using System.IO;
using System.Diagnostics;
 
namespace LogsCollector
{
    [DataCollectorTypeUri("datacollector://ShaiRaiten/LogsCollector/1.0")]
    [DataCollectorFriendlyName("Local Logs Collector")]
 
    public class LogsCollector : IDataCollector
    {
        private DataCollectionEvents Events;
        private DataCollectionSink dataSink;
        private XmlElement config;
 
        public void Initialize(System.Xml.XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink dataSink, DataCollectionLogger logger, AgentContext agentContext)
        {
            this.Events = events;
            this.dataSink = dataSink;
            this.config = configurationElement;
 
            Events.TestCaseEnd += new EventHandler<TestCaseEndEventArgs>(Events_TestCaseEnd);
        }
 
        void Events_TestCaseEnd(object sender, TestCaseEndEventArgs e)
        {
            try
            {
                List<string> folders = new List<string>();
                XmlNode currentNode = config.FirstChild;
 
                while (currentNode != null)
                {
                    if ((currentNode.Name == "Folder") && (currentNode.Attributes["FullPath"] != null))
                        folders.Add(currentNode.Attributes["FullPath"].Value);
                    currentNode = currentNode.NextSibling;
                }
 
                foreach (string folder in folders)
                {
                    string[] files = Directory.GetFiles(folder);
                    foreach (string file in files)
                        dataSink.SendFileAsync(e.Context, file, false);
                }
            }
            catch (Exception ex)
            { throw ex; }
        }
 
        public void Dispose()
        {
            //Unregister events
            Events.TestCaseEnd -= new EventHandler<TestCaseEndEventArgs>(Events_TestCaseEnd);
        }
    }
}
 
Download Demo Project

Enjoy.

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 1

shair — Mon, 11 Jan 2010 17:46:00 GMT

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 1

In my previous post I’ve talked about What is Diagnostic Data Adapters – No More No Repro!, this post will be about how to
create your own Diagnostic Data Collector.

Download Demo Project

In this post I’ll show you how to create a custom Log data collector that can be very helpful for many applications using local logs.

Below is an example of advanced custom data adapter I built for collecting performance data during a test. – I’ll get to this later…

Step 1 – Getting Started

Create a Class library project and add two references:

Microsoft.VisualStudio.QualityTools.Common
2. Microsoft.VisualStudio.QualityTools.ExecutionCommon.dll

You can find those assemblies C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\
(If you are not using 64bit operation system - C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\).

Step 2 – Create Data Collector Class

1. Add new class to your project with the Data Collector name, make sure the class defined as Public and add both using to the class:

using Microsoft.VisualStudio.TestTools.Execution;
using Microsoft.VisualStudio.TestTools.Common;
 
2. Add the Data Collector attributes 
 

[DataCollectorTypeUri("datacollector://Manufacturer/DataCollectorName/Version")]
[DataCollectorFriendlyName("Data Collector Name")]

3. Add IDataCollector interface and implement it.
This is what you should see:

public void Initialize(XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink dataSink, DataCollectionLogger logger, AgentContext agentContext)
{
    throw new NotImplementedException();
}
 
public void Dispose()
{
    throw new NotImplementedException();
}

Step 3 – Implement Custom Data Adapter

Using the DataCollectionEvents add the desire events for the Custom Data Adapter.

And define DataCollectionSink for storing files as attachments.

For Example:

private DataCollectionEvents Events;
private DataCollectionSink dataSink;
private const string LogPath = @"C:\Logs";
 
public void Initialize(System.Xml.XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink dataSink, DataCollectionLogger logger, AgentContext agentContext)
{
    this.Events = events;
 
    //DataCollectionSink - Diagnostic data adapters use a DataCollectionSink to store files and 
    //XML data for later attachment to bugs and test reports.
    this.dataSink = dataSink;
 
    Events.TestCaseEnd += new EventHandler<TestCaseEndEventArgs>(Events_TestCaseEnd);
}          
          

Now write the code to collect the logs from the specified folder.

void Events_TestCaseEnd(object sender, TestCaseEndEventArgs e)
{
    try
    {
        if (Directory.Exists(LogPath))
        {
            string[] files = Directory.GetFiles(LogPath);
            foreach (string f in files)
            {
                dataSink.SendFileAsync(e.Context, f, false);
            }
        }
    }
    catch (Exception ex)
    { throw ex; }
}
Step 4 – Install Custom Data AdapterEnd you’re almost done, Build the solution, and then copy the built assembly to -          
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\DataCollectors
 
Now create a new test (VS2010 – Coded UI Test) and define the new Data Adapter(Team System 2010 Beta 2 – Diagnostic Data Adapters – No More No Repro!).
I’ve built a simple WPF application that creates log file in C:\Logs.
       
 
 
Below image show a normal run of CodedUITest without selecting the data adapter.

Below image show a CodedUITest run with Logs Data Adapter selected.

Local Logs Folder

Full Code Sample:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.VisualStudio.TestTools.Execution;
using System.Xml;
using System.IO;
 
namespace LogsCollector
{
    [DataCollectorTypeUri("datacollector://ShaiRaiten/Logs/1.0")]
    [DataCollectorFriendlyName("Local Logs Collector")]
    public class LogsCollector : IDataCollector
    {
        private DataCollectionEvents Events;
        private DataCollectionSink dataSink;
        private const string LogPath = @"C:\Logs";
 
        public void Initialize(System.Xml.XmlElement configurationElement, DataCollectionEvents events, DataCollectionSink dataSink, DataCollectionLogger logger, AgentContext agentContext)
        {
            this.Events = events;
 
            //DataCollectionSink - Diagnostic data adapters use a DataCollectionSink to store files and 
            //XML data for later attachment to bugs and test reports.
            this.dataSink = dataSink;
 
            Events.TestCaseEnd += new EventHandler<TestCaseEndEventArgs>(Events_TestCaseEnd);
        }
 
        void Events_TestCaseEnd(object sender, TestCaseEndEventArgs e)
        {
            try
            {
                if (Directory.Exists(LogPath))
                {
                    string[] files = Directory.GetFiles(LogPath);
                    foreach (string f in files)
                    {
                        dataSink.SendFileAsync(e.Context, f, false);
                        
                    }
                }
            }
            catch (Exception ex)
            { throw ex; }
        }
 
        public void Dispose()
        {
            //Unregister events
            Events.TestCaseEnd -= new EventHandler<TestCaseEndEventArgs>(Events_TestCaseEnd);
        }
    }
}
Download Demo Project

Enjoy

Team System 2010 Beta 2 – Diagnostic Data Adapters – No More No Repro!

shair — Thu, 07 Jan 2010 19:40:24 GMT

Team System 2010 Beta 2 – Diagnostic Data Adapters – No More No Repro! – Part 1

What is Data Adapter?

Diagnostic Data Adapters will allow you specify various types of data to collect or how to affect the test machine when you run manual tests, automated tests, or both.
For example, a diagnostic data adapter might create an action recording, an action log, a video recording, or collect system information.
Additionally, diagnostic data adapters can be used to simulate potential bottlenecks on the test machine or reduce the available system memory.
For example, you can emulate a slow network to impose a bottleneck on the system.

How To Define Data Adapter?

You can define data adapters in two places – Microsoft Test & Lab Manager (manual testing) and Visual Studio 2010 (automated testing).

Microsoft Test and Lab Manager

Open MTLM and create a new Test Plan (Team System 2010 - Create a Test Plan [HE] – Screencast)

Visual Studio 2010 Beta 2

After you create a Test Project you will notice Local.testsettings file was created under “Solution Items” folder.

The bellow pictures shows two ways on how to open the Test Settings window.

Shai Raiten's Blog : Data Collectors

Test Attachment Cleaner

Test Attachment Cleaner

Teched 2010 - Applied Software Testing with Visual Studio 2010 – Done

Teched 2010 - Applied Software Testing with Visual Studio 2010 – Done

Tech-Ed 2010 – Applied Software Testing with Visual Studio 2010 – All In One

Tech-Ed 2010 – Applied Software Testing with Visual Studio 2010 – All In One

Microsoft Key Note At SIGIST 2010 - Test Automation - Done

Microsoft Key Note At SIGIST 2010 - Test Automation – Done

How To Create Custom DataCollector In Visual Studio 2010 – Part 2

How To Create Custom DataCollector In Visual Studio 2010 – Part 2

Step 1 – Add Configuration File

Step 2 – Initialize Configuration Element

Step 3 – Use Configuration Element

How To Create Custom DataCollector In Visual Studio 2010 – Part 1

How To Create Custom DataCollector In Visual Studio 2010 – Part 1

Step 1 – Getting Started

Step 2 – Create Data Collector Class

Step 3 – Implement Custom Data Adapter

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 2

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 2

Step 1 – Add Configuration File

Step 2 – Initialize Configuration Element

Step 3 – Use Configuration Element

Step 4 – Install Configuration File

Full Code :

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 1

VSTS 2010 Beta 2 – Diagnostic Data Adapters – Custom Adapter – Part 1

Step 1 – Getting Started

Step 2 – Create Data Collector Class

Step 3 – Implement Custom Data Adapter

Step 4 – Install Custom Data Adapter

Full Code Sample:

Team System 2010 Beta 2 – Diagnostic Data Adapters – No More No Repro!

Team System 2010 Beta 2 – Diagnostic Data Adapters – No More No Repro! – Part 1

What is Data Adapter?

How To Define Data Adapter?

Visual Studio 2010 Beta 2

Now Run and Open BUGS with a lot of data to help you and the developer solving it faster.