Forum member

DanielM

9 posts

Posts by DanielM

  1. Receiving test errors after updating to 3.29

    Thanks for the quick response. We were able to resolve the issue and found some UI related code that needed to use the Dispatcher. I'm still using the older version but I plan on upgrading soon and giving it another shot. Thanks again.

    20 Nov 2019 22:24 UTC

  2. Receiving test errors after updating to 3.29

    Just to add a little more information, in case it helps. I do have a couple of tests that I'm working to resolve an issue for where the message displayed in v3.22.1 is "System.InvalidOperationException : The calling thread cannot access this object because a different thread owns it." I see the issu…

    23 Oct 2019 20:15 UTC

  3. Receiving test errors after updating to 3.29

    Hello, I just recently updated from v3.22.1 to v3.31.1 and discovered I have a very similar issue as described here. The difference is turning the settings off didn't fix the issue. I tried to turn off both of the settings noted above but I still get the error. Then I individually turned each one…

    23 Oct 2019 19:54 UTC

  4. Run a category of tests in parallel but exclusively from other tests?

    You're right! I didn't perceive the messenger as having any state that might persist across tests. Turns out that assumption was incorrect. I resolved the issues by modifying my custom attribute to create and assign a brand new default instance (instead of preserving and reassigning to same instance…

    26 Jul 2018 18:08 UTC

  5. Run a category of tests in parallel but exclusively from other tests?

    We have a codebase that has a singleton Messenger class instance that is referenced statically (i.e. Messenger.Default). We create a stub the of the messenger class and assign it to the default property, on assembly startup, because most tests aren't concerned with the messenger behavior. For the ot…

    24 Jul 2018 18:14 UTC

  6. Manually associated test fixture with dependent class

    Hi Remco, Thanks for the speedy reply! Yes, I'm referring to the 'Run impacted tests automatically, others manually' mode. That is handy as we have 10's of thousands of tests and running them all is time consuming and just isn't necessary .... but it does help to warm my office in the winter mont…

    31 Oct 2017 04:46 UTC

  7. Manually associated test fixture with dependent class

    Hello, We have NCrunch configured to re-run tests automatically when changes are detected. This works great for large projects with lots of tests. I discovered that I have an issue similar to the one suggested here http://forum.ncrunch.net/yaf_postst328_Association-of-non-code--and-other-undetect…

    31 Oct 2017 04:07 UTC

  8. Only one of multiple TestCaseSource attributes respected

    Thanks that clears things up... it was a bit of a pain but I ended up getting a solution implemented. I modified the same extension methods I posted above to take a callerName (a string of some sort, testfixture name, or test case source name, that differs between test fixtures) and a Id. For each f…

    16 Feb 2017 19:59 UTC

  9. Only one of multiple TestCaseSource attributes respected

    I've read the posts both on this forum and NUnit's forum... In my case, I have multiple test fixtures that inherit from the same base Test Fixture. Each derived fixture uses [TestFixtureSource] that point to the same test data source. My test data source is a long string (a fragment of a text file) …

    13 Feb 2017 21:57 UTC