June 2011 - Posts

יצא Patch חדש ל–Visual Studio 2010 SP1 עבור כלי הבדיקות

פורסם בתאריך Jun 27 2011, 02:05 PM על ידי Eran Ruso

יצא Patch חדש ל–Visual Studio 2010 SP1 עבור כלי הבדיקות

לפני מספר ימים הוכרז על Patch חדש ל – Visual Studio 2010 SP1.

ה – Patch מכיל תיקוני באגים בעיקר עבור כלי הבדיקות, רשימה מלאה של התיקונים נמצאת בסוף הפוסט.

ניתן להוריד את ה – Patch מהלינק:

http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=36847

יש להתקין Visual Studio 2010 SP1 לפני התקנת ה – Patch.

צירפתי את תיאור הבעיות אותן פותר ה – Patch מאתר ההורדה:

An update rollup is available that resolves the following issues for the testing tools in Microsoft Visual Studio 2010 Service Pack 1 (SP1).

Issue 1

When you run tests on the test agent that is installed on a computer that has Visual Studio 2010 SP1 installed, the tests may not run, and the following error message is logged:

Attempted to access an unloaded AppDomain. (Exception from HRESULT: 0x80131014)

Issue 2

When you run a playback of a Coded UI Test on certain Windows Presentation Foundation (WPF) controls, a Microsoft.VisualStudio.TestTools.UITest.Extension.UITestControlNotFoundException exception occurs, and then you receive the following error message:

"Search may have failed at '<name>' <control type> as it may have virtualized children. If the control being searched is descendant of '<name>' <control type> then including it as the parent container may solve the problem."

Notes

One of the causes of this error message is that the WPF controls are deep in the UI control hierarchy. Therefore, the control cannot be addressed in the recorded QuerID UI control hierarchy in the UI map. After you install this update, the control can be addressed.
After you install this update, the following key is added to CodedUITestBuilder.exe.config/MTM.exe.config files to resolve this issue:
<add key="MaxLevelsForItemContainer" value="<desiredLevel>"/>
UI Test Framework searches the UI Hierarchy until <desiredLevel> to identify a parent container. By default, <desiredLevel> is set to 2. Set the value to an appropriate value for your situation.
If a high value is set, performance may be affected when a recording operation occurs.

Issue 3
When you try to create a work item from the Test Results pane in Visual Studio 2010 after you connect to a Team Foundation Server (TFS) server, a System.OutOfMemory exception occurs, and the creation operation fails. This issue usually occurs if the TFS server has many builds.

Issue 4

When some tests run in a build operation, some builds that are queued in a TFS server stop responding. Additionally, the following error message is logged in the build log:

Waiting to publish...
Publishing results of test run <build name> to http://<TFS server address>:8080/tfs/DefaultCollection...
The process cannot access the file '<directory>\data.coverage' because it is being used by another process.
Publish failed or canceled.

Note This issue occurs because the Mstest.exe process crashes. When a non-test thread encounters a nonfatal exception that is unhandled or an assertion failure, the Mstest.exe process crashes if code-coverage collector is enabled for the test run.
This issue may occur when tests run in an MSBuild script. MSBuild scripts skip the test run step.