Executing all tests when only one is chosen to debug

Gary Newport

September 30, 2021 09:01

Hi,

Recently I've noticed that whenever I try to debug or run one particular test all others in the solution are executed.

Gary

0

• 

  Jordan Western

  October 04, 2021 07:29

  Hi Gary Newport,

  Are you executing via the IDE or in a CI/CD pipeline?

  Can you share some details?

  Thanks, Jordan.

  0
• 

  Gary Newport

  October 04, 2021 08:11

  Jordan,

  This is when I'm running from within visual studio 2019.

  Gary

  0
• 

  Jordan Western

  October 04, 2021 08:59

  Hi Gary Newport,

  Are you only selecting one test from the test explorer window? (i.e. right click on the test, click debug).

  Can you try and illustrate to me the issue?

  0
• 

  Gary Newport

  October 04, 2021 09:48

  Jordan,

  Yes, I have a suite of test reading, writing information to the azure blob store, I've changed the tests so each test will write to its own container. I find that when I right-click debug a particular test and check azure storage explorer, all the containers have been created and contain data before the selected test hits its first break point.

  I've got the same results lots of other libraries.

  This has only started happening in the last month or so, so I've tried to work around the issue by simplifying the tests.

  Currently using <PackageReference Include="SpecFlow.MsTest" Version="3.9.8" 

   

  0
• 

  Jordan Western

  October 06, 2021 08:11

  Hi Gary Newport,

  This would be very difficult for me to suggest anything without taking a look at the project.

  I can't think of anything that could be causing the issue other than something inside of your code.

  Maybe you can try and share the flow of execution with some code examples?

  0

Please sign in to leave a comment.