When an assertion in a test fails, you get the full stack trace of the AssertFailedException, which is noisy. For instance:

Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.HandleFail(String assertionName, String message, Object[] parameters)
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual, String message, Object[] parameters)
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual)
at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:[some likely really long path]\RectangleTests.cs:line 22

Of all the above information, the only pertinent information is the message text of the exception and the bottom of the stack where the assertion failure happened. For instance:

Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:\users\floyd.may\documents\visual studio 2012\Projects\TestInheritance\TestInheritance.Tests\RectangleTests.cs:line 22

Ideally, for MSTest, NUnit, etc., each testing frameworks' specific assert fail exceptions should get special treatment to eliminate the noise.