![]() Attributes are used to indicate which tests may run in parallel and how they relate to Parallel Test Execution, although it is possible to use both in theīy default, no parallel execution takes place. This is a completely separate facility from Engine The NUnit 3.0 framework can run tests in parallel within anĪssembly. I've checked the thread ids in different tests and they all are different. If threads are different(between a test and the setup method) then the action under test gets executed asynchronously and my tests fail. ![]() UPD: I'm using MVVM Light DispatcherHelper.Initialize()(inside ) to store the dispatcher object which is later used by a couple of tests. I run it with ReSharper but also tried with MSVS add-in. Moreover, I've tried to add the following attribute: - no luck.ĭoes anybody know how to change this behavior? I've read the documentation and it states that by default tests aren't run in parallel but in fact they are! I have some initialization in which is thread-dependent and it seems I can't do anything to force NUnit to run my tests sequentially. It might look like desirable behavior but I didn't ask for it and actually it broke some of my tests. I have the latest NUnit(3.2.0) installed and I have all my tests run in parallel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |