All geek questions in one place

After the update, Unit Tests starts a timeout in an hour, when they finished in 15 minutes

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. The block now tests the timeout after 50 minutes, when they finish after about 15 minutes. These tests are run on JetBrains TeamCity 6.0.2 on our dev server. Does anyone know what might cause this? Some individual tests take up to 8 minutes.

Thanks,

Jason

+4
source share
1 answer

Well, I figured it out. On our domain object classes, there were places where we had validators (MS Enterprise Library) for public properties. Validators referred to keys from the project resource file. We had nonexistent resource keys in our validators. This caused errors due to which our unit tests timed out. I believe .NET 4.0 is more rigorous. Thanks for all the suggestions. - Jason -

0
source

Source: https://habr.com/ru/post/1343816/

More articles:


All Articles