While doing MSTest, Is there criteria in which Visual Studio version it should be created? I tried it in Visual Studio 2017 and it is not working.

Got it working, rraghvani_0-1694006110845.png The unit test project must contain the following references, rraghvani_1-1694006161964.png for MSTest to work.

MSTest Configuration | SmartBear Community

13 Replies

rraghvani

Champion Level 3

2 years ago

See https://learn.microsoft.com/en-us/visualstudio/test/run-a-unit-test-as-a-64-bit-process?view=vs-2022

MSTest.exe is 32 bit

Sigcheck v2.90 - File version and signature viewer
Copyright (C) 2004-2022 Mark Russinovich
Sysinternals - www.sysinternals.com

c:\program files\microsoft visual studio\2022\professional\common7\ide\MSTest.exe:
        Verified:       Signed
        Signing date:   19:45 06/04/2023
        Publisher:      Microsoft Corporation
        Company:        Microsoft Corporation
        Description:    Test Execution Command Line Tool
        Product:        Microsoft« Visual Studio«
        Prod version:   17.0.33606.225
        File version:   17.0.33606.225
        MachineType:    32-bit

rraghvani
Champion Level 3
2 years ago
What is not working?

Are you using this?

rraghvani_0-1693988174406.png
- sinis
  Frequent Contributor
  2 years ago
  No, I am using this
  sinis_1-1693988318018.png
  
  whenever I try to run this, There is error showing like "no test to execute". And inside the options in TestComplete, we give MSTest.exe to make MS tests run
  sinis_2-1693988401963.png
  And when I checked Internet, I found that this issue is common and now most of the tests are run using vsconsole.exe and MSTest is not used in latest versions of Visual Studio
rraghvani
Champion Level 3
2 years ago
I'll have a look at this - I've just notice that the path doesn't look correct,

rraghvani_0-1693989241843.png

It should be using '\' backslash?
- sinis
  Frequent Contributor
  2 years ago
  Corrected, but still the same issue
rraghvani
Champion Level 3
2 years ago
Are you able to run,

mstest /testcontainer:[insert your .dll here]

from the command prompt?

I'm not able to run mstest because it's deprecated. I'm using VS2022

rraghvani_0-1693997719033.png
rraghvani
Champion Level 3
2 years ago
Got it working,

rraghvani_0-1694006110845.png

The unit test project must contain the following references,

rraghvani_1-1694006161964.png

for MSTest to work.
- sinis
  Frequent Contributor
  2 years ago
  rraghvani I am using VS2017 I am not getting these references.
  - sinis
    Frequent Contributor
    2 years ago
    rraghvani I got it now. It is working. Thanks
rraghvani
Champion Level 3
2 years ago
Since mstest.exe deprecated, it's worth requesting SmartBear to update to use vstest.console.exe.
- sinis
  Frequent Contributor
  2 years ago
  rraghvani when I try to run mstests, this error is coming. Can we only run tests which are build in Any CPU configuration inside testcomplete? I have build the assembly in x64 bit.
  
  sinis_0-1694418115374.png
rraghvani
Champion Level 3
2 years ago
If your application under test is x64, then you must use TestComplete x64.
- sinis
  Frequent Contributor
  2 years ago
  I have been using TestComplete x64. But inside visual studio , I have given platform target as x64. When I am running with this platform, there is error in test complete. But when I use " Any CPU" as platform , it is working fine. But for my application, it is necessary that I need to use x64. I am thinking whether MSTest.exe is configured to run 32 bit DLLs.
  sinis_0-1694758892054.png