Forum member

kalebpederson

25 posts

Posts by kalebpederson

  1. Troubleshooting build of non-SDK style project using PackageReference

    [quote=Remco] ... Can you try using ProjectName instead of MSBuildProjectName when overriding the BaseIntermediateOutputPath property?[/quote] Yes, that fixed it! We did have a mix of non-SDK style projects and with other SDK style projects. About half way through the solution NCrunch failed t…

  2. Troubleshooting build of non-SDK style project using PackageReference

    [quote=Remco]Hi Kaleb, Thanks for sharing this issue in such detail. NCrunch should normally detect the project.assets.json file (along with its related 'obj' files) and copy this into the workspace with some minor manipulation. How are your projects structured in regards to project.assets.js…

  3. Troubleshooting build of non-SDK style project using PackageReference

    I'm working with a monolith that uses a [url=https://github.com/microsoft/MSBuildSdks/tree/master/src/Traversal]traversal build[/url] to build a set of projects that are available to us developers in a set of different solution files. I'm now trying to get NCrunch working with these solutions. I was…

  4. Building Large Source Trees Spanning Solutions

    [quote=Remco;11428]When NCrunch creates a workspace for your project, it does so with consideration to upwards relative references by padding out the workspace directory. In this way, all dependencies should be contained completely within the workspace. It's not clear to me why this particular f…

  5. Building Large Source Trees Spanning Solutions

    Hi all, Not too long ago we switched from an extremely large single-solution project to a multiple solution project whose build system is based on the recommendation in "Appendix B, Building Large Source Trees" of "Using MSBuild and Team Foundation Build". The Appendix containing a full descripti…

  6. Add expected test duration as engine mode criteria

    I'm using NCrunch for integration testing as well as unit testing and I'd like to be able to create an engine mode that will only run tests that are expected to take less than a given amount of time. For example, I might want to run all tests that are expected to take less than 250ms. Thank you f…

  7. Only one of multiple TestCaseSource attributes respected

    [quote=Remco;4309]Thanks Kaleb. I've met people within the industry with strong opinions on tests always having consistent and deterministic behaviour.[/quote] For unit tests, I agree with this. I actually use the current time as an indicator that the date/time doesn't matter nor change the flow…

  8. Only one of multiple TestCaseSource attributes respected

    [quote=Remco;4305]Is this DateTime value consistent between test runs? If it isn't, it will certainly cause problems. ...Unfortunately there isn't really an ideal solution to this with the design of NCrunch - test names need to be consistent and unique in order for it to work correctly. [/quote…

  9. Only one of multiple TestCaseSource attributes respected

    I just improved my ToString() methods to find that NC considers the old tests as failures and gives the following message: [quote]This test was not executed during a planned execution run. Ensure your test project is stable and does not contain issues in initialisation/teardown fixtures.[/quote]…

  10. Only one of multiple TestCaseSource attributes respected

    I'd personally prefer to see behavior consistent with the NUnit test runner which is to run all the tests and simply display them with duplicates. Resharper's test runner does the same. I'm probably going to change my ToString() method so I can distinguish between them, so do what you consider t…

  11. Only one of multiple TestCaseSource attributes respected

    Your description is very close. I'm not explicitly creating the TestCaseData as you're describing, but instead NC seems to take the name implicitly from the ToString() of the object: [code=csharp] public class Data { public int Value { get; set; } public Data(int value) { Value =…

  12. Only one of multiple TestCaseSource attributes respected

    Hi, just a quick bug report. If a NUnit test contains multiple TestCaseSource attributes, only one of the two is executed. For example: [code=csharp][Test] [TestCaseSource("DataSource1")] [TestCaseSource("DataSource2")] public void Children_property_is_empty(Variable variable) { Assert.…

  13. "Take me to first failing test" keyboard shortcut

    Sounds great, thanks!

  14. "Take me to first failing test" keyboard shortcut

    [quote=Remco;2493]When navigating to a failed test, there are two points of navigation that are of interest: 1. The entry point of the test 2. The deepest accessible point of failure on the failing test's exception call stack [/quote] I think it depends. The main question I'm asking myself …

  15. "Take me to first failing test" keyboard shortcut

    Directly related to the recently posted "Automatically select first broken test in NCrunch Tests Window," when I'm TDDing it would be great if I had a keyboard shortcut that opened up the test file that contained the failing test and navigated to that test. I'll typically use Resharper's Ctrl-Dash, …

  16. Debugging tests that require an external dll

    [quote=Remco;2409]Hi Kaleb, ... Something to watch out for is that NCrunch will only ever use the default build configuration that is specified in the .proj file, and it will ignore the currently selected build configuration in Visual Studio. I wonder if this may have been the source of some of y…

  17. Debugging tests that require an external dll

    [quote=Remco]Hi, thanks for posting![/quote] And thanks for responding. [quote=Remco] In some application domains, the GetAssemblies().Select(x => x.Location) code will cause the exception you've described to be thrown. I've updated the documentation with an adjustment to this to avoid refer…

  18. Debugging tests that require an external dll

    I've read through the test troubleshooting page but I'm still having problems getting a few (integration-like) tests to work in NCrunch. The tests run fine in the nunit.console test runner as well as the Resharper test runner. I have the following projects and dependencies: [code=plain]MyProj…

  19. Coverage shows black when tests cover code

    And a few other details: I'm using a single library project with a single file in it, whose contents are listed above. I've pulled in the latest Moq and NUnit from NuGet. Let me know if there are any other details that you need. Thanks. --Kaleb

  20. Coverage shows black when tests cover code

    I was working on a kata, of sorts, this morning and was able to reproduce this. Here's a complete testcase: [code=csharp] using System.Collections.Generic; using NUnit.Framework; namespace TddPresentation { [TestFixture] public class PasswordCheckerTest { private PasswordChecker _c…