Has anyone had any experience with running test execute through cruisecontrol.net and msbuild? What im running into is this ... the test runs and finishes, then test executes memory usage goes all over the place anywhere from 40 megs to 1.2 gigs of memory ... it fluctuates for a while then goes back down to 20-30 megs and just sits there. Eventually the timeout cruisecontrol task kills everything. I get a resuilt file but a failure is reported back to cruisecontrol through msbuild.
Automated QA has an assembly they release with their enterprise edition of testexecute. It is callable from MSBUILD which is part of the .NET SDK. MSBUILD tasks are callable from cruisecontrol.net with is an automation interface. It kicks off test runs and monitors their status.
Im sure the msbuild syntax just spawns TE from the command line, and its syntax is as follows.
<!-- Target -->
But I wonder if it has to do with the command line. See, when you're running TE from a pure command line, you can add a switch to automatically exit TE once the project suite is complete. Does such a thing exist in that assembly?
We will try to reproduce the problem when TestExecute is started this way. Please give me some additional information about your environment:
- Windows version;
- .NET Framework version;
- CruiseControl .NET version.
BTW, what account do you use to run CruiseControl and MSBuild? Are they started under the account of the user who is currently logged in?