We upgraded our unit test project from .NET 3.5 to .NET 4.0. We also upgraded NUnit from 2.5.2 to 2.59. Now the unit tests time out after 50 minutes when they used to finish in about 15 minutes. These tests are run on JetBrains TeamCity 6.0.2 on our dev server. Does anyone know what could cause this? Some individual tests take up to 8 minutes now.
Thanks,
Jason
Well, I figured it out. There were places on our domain object classes where we had validators (MS Enterprise Library) on public properties. The validators were referencing keys from the project's resource file. We had nonexistent resource keys in our validators. This was causing the errors which caused our unit tests to time out. I guess .NET 4.0 is being more strict. Thanks for everyone's suggestions. - Jason –