unit testing - Why does MSTest fail to deploy some test input files when there are more than 128 tests? -


We run automated tests on a build server that uses Jenkins to view source code, create and test MSTest runs by running it on. By the time we did not add 129th unit test, everything worked fine. Then some tests fail mysteriously which fails the examinations, all input files that need to be deployed in the TestResults directory. However, when 129th test is added, those input files are not deployed! Note that other tests require input files but they deploy.

Whatever we have done:

  • It does not matter which test project is added to the 12 9th Unit Test or what is in the new test (example To assign: Array aqual (1, 1);)
  • Manually run MSTE on the command line (Visual Studio 2010 x86 tools) when building server when logging in as my build server 128 Even more tests occur, this test fails even though There is no likelihood of doing this with S, or the fact that automated tests are being run under different user accounts (systems).
  • Copy the code created from the build server to my laptop and the same mstst the command there are all 129 exams on my laptop, even if the build machine and my laptop MSTeist (10.0.30319.1) are the same Using the version.

    Has anyone seen anything like this? There should be something that happens only when more than 128 tests are added, and which can be on a machine but not the second! What is 128 coincidence? I know that this is a significant number in computing.

    After more investigation, it seems that there is some problem with the MSTT or some agents under it's cover Makes a call. See for details.

    But when I installed Visual Studio 2013 on the build server machine, which was already installed, in addition to VS2.2010, all 129 tests will be passed when both MSTTs are prompted by the VS2010 command shortly And when you walk through Jenkins, note that VS2013 is not used to build or run tests; I have not even opened it on Build Server; Just install it!

    will affect the way the VS2013 is installed, just as MST will run for VS 2010. Maybe it uses MSTest or some agent, or changes some ambient variables, or ...?! Therefore, there is probably a small fix for this, but now the addition of VS-2010 is to install VS 2013 in addition to VS 2013 if you want to execute more than 128 exams using MSTE for VS-2010. Surely Microsoft knows about this issue ?!

Comments

Popular posts from this blog

ios - Adding an SKSpriteNode to SKScene from a child SKSpriteNode -

Matlab transpose a table vector -

c# - Textbox not clickable but editable -