I will contact you through support channel regarding this.
you have to handle the exception and print to console or Parasoft Even details.
One possible cause is corrupted Visual Studio's Component Model Cache, which can prevent C++test from launching.
To clear the Component Model Cache, try to run cpptestcli with the -clearcmc option.
Let us know if this does not help.
Yes, that is correct.
I am afraid dotTEST currently does not support UWP projects.
There is no lock/unlock capability within the SOAtest Desktop. If you are using the Continous Testing Platform thin client, it does allow you to lock individual .tst files - although I'm guessing that's not quite what you want because you probably want to lock everything in the entire project.
please make sure that rule parameters are correctly set up and that the _logger.Error call should be recognized as "log" method based on parameters definition.
If you believe rule parameters are correctly set up, could you please provide compilable/simplified code which shows the problem?
For linking the rules documentation it is enough to create a new properties file with the following properties:
for local documentation
or for online documentation
Next, refer to that file from Configure> Build Settings > Publish Parasoft analysis results > Settings
You can do it using SOATest Server rest api:
dotTEST can skip *.Designer and autogenerated files (files which have <AutoGen> node defined in a project file). This can be done by specifying the setting:
Also, you can define file filters in test configuration using DTP or Test Configuration Editor (released with dotTEST 10.4.0):
If this is not an option, but you have control over how your files are generated, then you can generate area suppressions in your files or marking your files as autogenerated with some specific tags and then set up test configuration accordingly.
As a last resort, you can define -exclude pattern in dottestcli.exe command line to explicitly exclude those files from analysis scope.