tag:help.appveyor.com,2012-11-13:/discussions/problems/12076-unable-to-filter-assemblies-when-running-tests-all-assemblies-are-always-discoveredAppVeyor: Discussion 2018-10-19T08:18:40Ztag:help.appveyor.com,2012-11-13:Comment/447262052018-02-14T10:56:28Z2018-02-14T10:56:28Zunable to filter assemblies when running tests, all assemblies are always discovered<div><p>Hi Alan,</p>
<p>I do not see build URL, but the fact that you are using <code>Visual Studio 2017</code> and run <code>dotnet restore</code> makes me think that you are running .NET Core tests. Test <strong>assembly</strong> detection and filtering works for classic .NET Framework tests. For NET Core tests we just detect all NET Core tests <strong>projects</strong> and run <code>dotnet test</code> against them. Please watch <a href="https://github.com/appveyor/ci/issues/2022">this</a> issue for a fix. It should be done soon. For now workaround is using <code>test_script</code> and run <code>dotnet test</code> against project you need.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/447262052018-02-14T13:15:44Z2018-02-14T13:15:44Zunable to filter assemblies when running tests, all assemblies are always discovered<div><p>Ah, that's exactly it, good to know I'm not crazy.<br>
Thank you for the work around, ..I will try that now.</p>
<p>regards</p>
<p>Alan</p>
<p>Alan Hemmings</p>
<p><a href="http://www.goblinfactory.co.uk">http://www.goblinfactory.co.uk</a></p>
<p>Director, Goblinfactory Limited<br>
<a href="http://www.goblinfactory.co.uk">www.goblinfactory.co.uk</a><br>
Mobile - +44 (0) 7734 157754<br>
<a href="mailto:goblinfactory@gmail.com">goblinfactory@gmail.com</a></p>
<p>Registered in England & Wales, Company No. 4521933, CPC1, Capital Park,<br>
Fullbourn, Cambridge, CB21 5XE</p></div>goblinfactory