Forum member

jnm236

57 posts

Posts by jnm236

  1. Tests not discovered in net462 CPS .csproj

    It works great for the CPS test projects. I have an odd behavior, no idea if it is related. One of the test projects ran (which are all CPS now) and a single test failed. I ran the test a bunch more times. Later on, NCrunch stopped running tests for that project and I saw that it the project w…

  2. Tests not discovered in net462 CPS .csproj

    For the GAC issue, I actually don't think it's your fault. See my second comment: https://github.com/dotnet/roslyn-project-system/issues/1739#issuecomment-286236502 Somewhere in the course of fixing the GAC issue and other issues like [url=https://github.com/dotnet/roslyn-project-system/issues/1…

  3. Tests not discovered in net462 CPS .csproj

    Thanks Remco! Much appreciated! One of my test projects is now working properly with NCrunch. The only weird thing with this project is that it gives this warning, even though .NET Core is not in the picture: [quote]The dotnet package restore command timed out: "C:\Program Files\dotnet\dotnet.…

  4. Tests not discovered in net462 CPS .csproj

    We are motivated to move away from the old .csproj + project.json for our net462 projects. Building, discovering, running and debugging works perfectly in VS2017 RTM (NUnit test adapter extension installed) and in ReSharper 2017.1 EAP 4. NCrunch 3.5 (and NCrunch 3.2) builds but does not discover…

  5. 3.2 installer mistakenly thinks VS2017 setup failed, no way to override this

    Beautiful!

  6. 3.2 installer mistakenly thinks VS2017 setup failed, no way to override this

    This is a brand new installation of Windows. I needed to build for net20, so I went to "Turn Windows features on or off" and checked the .NET Framework 3.5 box. Then I restarted. Then on a whim I tried the NCrunch installer again and it worked fine. I hadn't run the VS installer before or after …

  7. 3.2 installer mistakenly thinks VS2017 setup failed, no way to override this

    Yes, I'm still having the problem. I didn't think of manual installation. I will do that, thanks!

  8. 3.2 installer mistakenly thinks VS2017 setup failed, no way to override this

    I updated VS2017. It said I needed a restart and I restarted. Once restarted, it was already finished installing and ready to go. At no point did any error message show up, nor was there any sign of failure. So, after the restart, I ran the NCrunch 3.2 installer. It maintained that the VS instal…

  9. Unnecessary .ncrunchproject files

    > If this is moved into the .user file, people will get notified of this for projects that are already configured by other team mates and have been built by NCrunch correctly. This would be preferable to me. Anyway, things change. I wouldn't want this info checked into source control because it'…

  10. TestCaseSource code always shows empty coverage

    NCrunch shows code coverage dots for the lines in the AllDbContexts method but they are always empty. NUnit executes this method during test discovery and then NCrunch only tracks coverage in the execution stage where it does not rerun AllDbContexts. Ideally NCrunch [i]would[/i] track the execut…

  11. Unable to exclude tests based on category

    In the process of building a repro, I discovered that I was mistaking the cached failure state appearing in the Tests window for NCrunch continuing to run the test. For some reason, I was expecting the test to disappear from the Tests window. I rely on the errored states in the NCrunch window all…

  12. netstandard support

    Thanks. My preference to know about shiny new bits will likely override. :')

  13. netstandard support

    3.2 is fine. If I might ask for a tiny feature... some applications give you an option to "ignore this version" so that you don't have to click through upgrade prompts every time you open them.

  14. Unnecessary .ncrunchproject files

    I have 21 .ncrunchprojects getting created containing nothing but `<PreviouslyBuiltSuccessfully>True</PreviouslyBuiltSuccessfully>`. I don't mind it in an .ncrunchproject.user or ideally some cache location not mixed with settings because it's not really a setting, but I believe .ncrunchproject g…

  15. Unable to exclude tests based on category

    I've deleted the My Computer modes, so now I have the four shared modes left. > To fully exclude all integration tests from automatic execution, you need to adjust the 'Tests to execute automatically' setting for each of the engine modes. I should have mentioned that I had done this for all e…

  16. Unable to exclude tests based on category

    I'm using NCrunch 3.2.0.3 and VS2015. I need some way to exclude integration tests from running automatically because they take a lot of resources. All my integration tests have the category "Integration" applied. The only settings window that seemed suitable for this is the Customize Engine …

  17. netstandard support

    I'm running into the exact same thing as well on VS2015 and NCrunch 3.3.0.6. I downgraded Humanizer to 2.0.1 on all projects and it still says "The type or namespace name 'Humanizer' could not be found (are you missing a using directive or an assembly reference?)" On a project referencing Entity…

  18. Duplicate test rows with conflicting states

    NCrunch has not given any warnings. This is the code from the one that was just bothering me: [code=csharp] public static IEnumerable<TestCaseData> AllGridControls() => from type in typeof(BaseView).Assembly.GetTypes() where type.IsSubclassOf(typeof(Control)…

  19. Duplicate test rows with conflicting states

    I have NUnit tests with a number of parameterized test cases. NCrunch displays all the test cases in the Tests window underneath the test row, but then it duplicates five of them at the bottom and doesn't update the state. They say "Running (first time)" and "Pending, impacted" while the copy above …

  20. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    I don't want to redesign. That would mean tracking what should be thirty separate test cases in a single test case, which makes it harder to see what exactly I'm affecting. So because I'm still somewhat in the market (haven't bought very far into NUnit), and I hate having to choose between NCrunc…