{"action":"closed","issue":{"url":"https://api.github.com/repos/xunit/resharper-xunit/issues/25","labels_url":"https://api.github.com/repos/xunit/resharper-xunit/issues/25/labels{/name}","comments_url":"https://api.github.com/repos/xunit/resharper-xunit/issues/25/comments","events_url":"https://api.github.com/repos/xunit/resharper-xunit/issues/25/events","html_url":"https://github.com/xunit/resharper-xunit/issues/25","id":54851077,"number":25,"title":"Tests stay in running state when assertions are not met, instead of just failing","user":{"login":"QFrameTK","id":8927289,"avatar_url":"https://avatars.githubusercontent.com/u/8927289?v=3","gravatar_id":"","url":"https://api.github.com/users/QFrameTK","html_url":"https://github.com/QFrameTK","followers_url":"https://api.github.com/users/QFrameTK/followers","following_url":"https://api.github.com/users/QFrameTK/following{/other_user}","gists_url":"https://api.github.com/users/QFrameTK/gists{/gist_id}","starred_url":"https://api.github.com/users/QFrameTK/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/QFrameTK/subscriptions","organizations_url":"https://api.github.com/users/QFrameTK/orgs","repos_url":"https://api.github.com/users/QFrameTK/repos","events_url":"https://api.github.com/users/QFrameTK/events{/privacy}","received_events_url":"https://api.github.com/users/QFrameTK/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":32,"created_at":"2015-01-20T07:15:08Z","updated_at":"2015-04-01T14:47:27Z","closed_at":"2015-04-01T14:47:27Z","body":"![image](https://cloud.githubusercontent.com/assets/8927289/5813259/06d6dd02-a07b-11e4-8777-f645e59609e9.png)\r\n\r\nSometimes, when a tests fails (example: nhibernate schema validation, automapper assertconfiguration valid, but also business logic tests (are all properties saved to the db, for example), the test runner ends up in a state where it says that the test is still running, and it never gets out of this state anymore (see screenshot). No other tests below these tests in the unit test sessions tree are being executed.\r\n\r\nWhen debugging, you can actually see the assertion failures, and when you then continue the debug session, it ends up in this forever running state as well.\r\n\r\nBefore, I was using R#8, nothing was wrong. Another dev on my team with R#8 had the issue already. Now we have both upgraded to R#9, and are both facing the issue. 2 other developers on the team don't face the issue, and our CI server (TeamCity) isn't showing this issue either.\r\n\r\nMy configuration:\r\n\r\n- Visual Studio Professional 2013, version 12.0.31101.00 Update-4\r\n-  Resharper 9.0 Update 1 (Build 9.0.2014129.130142)\r\n- XUnit.net Test Support for ReSharper 9 2.0.1\r\n\r\nAny clue what might be causing this?"}}