Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Console execution troubles

    Hi, thanks for sharing this issue. The problem you're experiencing with the package restore is caused by the 'msbuild /t:Restore' failing when this step is executed by the console tool. It's possible you have the machine locked down so it's unable to access Nuget or there is otherwise something …

    06 Jun 2018 19:51 UTC

  2. Ncrunch does not copy empty folder to it's workspace.

    Hi Daniel, Thanks for sharing this problem. Could you clarify the purpose of this pre-build event? Is this trying to copy files from another project in your solution? If so, this may break [url=https://www.ncrunch.net/documentation/considerations-and-constraints_project-atomicity]NCrunch's pro…

    06 Jun 2018 11:57 UTC

  3. TeamCity distributed NCrunch is very slow

    [quote=robert-j-engdahl;12295] It is great that you have auto-batch size already. I agree setting a default would be redundant. How will tests with unknown execution times be handled in that setup, and could [AutoData] cause known tests to seem unkown?[/quote] By default, NCrunch considers a t…

    06 Jun 2018 11:52 UTC

  4. TeamCity distributed NCrunch is very slow

    The 'batching' of tests is very dynamic, as NCrunch will try to put faster running tests into bigger batches. You'll find that if you have 1000 tests with a running time of <1ms, they'll usually all land in the same task. Slow running tests will generally end up in small batches, and very often ca…

    06 Jun 2018 10:51 UTC

  5. ASP.NET Core 2.1 integration tests

    To update everyone on this issue, we've taken a deep look at it, and it's not good. This package works by hard-baking the location of the web project into the test project's binary. So if the web project moves relative to the test project, everything breaks. Given the current design of NCrunch,…

    06 Jun 2018 06:22 UTC

  6. Log output within OneTimeSetup? [NUnit]

    This will work when applied on a normal fixture, but a SetUpFixture is special. This is because according to NCrunch, A SetUpFixture isn't actually a test. It has no representation in the actual set of test results, therefore it cannot hold a result or a trace output.

    05 Jun 2018 12:33 UTC

  7. UI hangs for ~3 sec each time when running automatically

    It's quite possible this is being caused by garbage collection in the IDE process. Basically, the GC has the power to pause the process for entire seconds at a time to perform heap compactions. This happens longer and more frequently when there is high memory traffic in the process, which is bas…

    05 Jun 2018 12:27 UTC

  8. Log output within OneTimeSetup? [NUnit]

    Under NCrunch, this documentation isn't completely accurate. This is because NCrunch actually seizes the Console stream out from under NUnit and takes control over it. For this reason, using Console.Write or Debug.Write will always result in the trace output being captured in the NCrunch log, rega…

    05 Jun 2018 11:31 UTC

  9. TeamCity distributed NCrunch is very slow

    [quote=robert-j-engdahl;12281]It appears the AtomicAttribute can be applied to assemblies as well. So it would be relatively easy for us to test if that improves speed (there are still 72 of them, so there is something to be parallelized). I'll keep you posted on how that goes.[/quote] It can, …

    05 Jun 2018 11:16 UTC

  10. TeamCity distributed NCrunch is very slow

    NCrunch doesn't have an option to directly control the batching of tests, outside of [url=https://www.ncrunch.net/documentation/reference_runtime-framework_atomic-attribute]AtomicAttribute[/url]. Though in all honesty, given the structure of your solution I don't think you're going to make any bi…

    05 Jun 2018 09:12 UTC

  11. UI hangs for ~3 sec each time when running automatically

    Hi Kieren, Thanks for sharing this issue. We're extremely careful to stay off the UI thread under NCrunch, so I'm not sure if this is being caused by us. The quickest way to know is to launch a second instance of VS, and attach a debugger to the first instance. When the first instance is han…

    05 Jun 2018 09:06 UTC

  12. TeamCity distributed NCrunch is very slow

    The benefits of distributed processing on end-to-end runs generally tend to favour solutions with a large number of medium to slow running tests. By this, I mean tests with a running time of 10 seconds up to about 10 minutes. When working with large test suites of very fast running tests, the over…

    05 Jun 2018 06:05 UTC

  13. Cannot resize column in covering test popup

    Thanks for sharing this problem. This looks like it may be a recent development ... it's happening on my end too. We'll take a look at this and see if we can get it fixed :)

    04 Jun 2018 22:39 UTC

  14. TeamCity distributed NCrunch is very slow

    Hi, thanks for sharing this issue. The problem with the resetting ping issue is caused by a diagnostic message that accidentally went out with the release build. Probably, this may have some impact on performance, though I haven't measured it in detail yet. I recommend turning your logging off …

    04 Jun 2018 22:38 UTC

  15. Upgraded Web Project Not Building

    Try the following: - Wipe the NCrunch cache file as it exists on the build server - Ensure you have a fresh checkout of the source code on the build server (remove any cached copies) - Try configuring your build server to use a local user to run the console tool, which has access to the desktop…

    04 Jun 2018 22:28 UTC

  16. Code Coverage Markers Misaligned

    There is a known issue where CodeLens changes the vertical size of some lines of code (notably the first line of constructors). This causes the NCrunch markers to look a bit out of place on these lines, as they are aligned with the top of the line rather than the bottom. I've had a bit of a brai…

    04 Jun 2018 22:19 UTC

  17. .NET Core 2.0 Support with re-located build folder

    It doesn't look like we have any environment variables of that description during the load of projects .. at least not right now. It occurs to me though that with the new CPS project systems inferring many of the build properties from the project file name that we should be trying to add something …

    04 Jun 2018 21:43 UTC

  18. .NET Core 2.0 Support with re-located build folder

    It should still be possible to redirect your OutputPath without introducing any problems. The issue here is caused by the location of the generated files inside the 'obj' directory. The problem is caused by technical limitations with MSBuild, basically: - We need to be able to run MSBuild over …

    04 Jun 2018 11:44 UTC

  19. .NET Core 2.0 Support with re-located build folder

    It looks like this problem is being caused by a custom build override inside the Directory.Build.Props file: <BaseIntermediateOutputPath>$(RootFolder)Build\obj\$(MSBuildProjectName)\</BaseIntermediateOutputPath> Do you know why this has been redirected to a different location? By placing the …

    04 Jun 2018 10:09 UTC

  20. .NET Core 2.0 Support with re-located build folder

    Hi, thanks for posting. With the amount that .NET Core has moved, I don't have high expectations on a release as old as v3.12 working correctly. I'd be willing to bet that we've already fixed this in a later build. I've just dropped a short evaluation license on your website account. You're …

    04 Jun 2018 09:20 UTC