I had been running all my tests for a long time using Build-Deploy-Test workflow (http://social.technet.microsoft.com/wiki/contents/articles/tfs-2010-build-deploy-test.aspx)
Suddenly one day, the test runs started getting aborted and there was no specific log which pointed to the root cause.
To find the root cause, I ran all the tests locally from Visual Studio and tried to publish the results against a build from the Test Results window.
The publish failed with the error:
Failed Invalid character in Assert.AreEqual failed. Expected:xxx Actual:yyy
The problem was that xxx and yyy had some invalid characters which was causing the publish to fail. I fixed the test by comparing expected and actual and doing Assert.Fail() if they didn't match. Thus, the invalid characters were not logged to console and the publish started to succeed.
Problem solved and the test runs started getting completed.
Suddenly one day, the test runs started getting aborted and there was no specific log which pointed to the root cause.
To find the root cause, I ran all the tests locally from Visual Studio and tried to publish the results against a build from the Test Results window.
The publish failed with the error:
Failed Invalid character in Assert.AreEqual failed. Expected:xxx Actual:yyy
The problem was that xxx and yyy had some invalid characters which was causing the publish to fail. I fixed the test by comparing expected and actual and doing Assert.Fail() if they didn't match. Thus, the invalid characters were not logged to console and the publish started to succeed.
Problem solved and the test runs started getting completed.
No comments:
Post a Comment