PEX executable VS 2015 RC - pex

Is there a command line or API method to run explorations and generate tests for PEX in VS 2015? The docs for the previous version refer to a command line mode via pex.exe. There is a Microsoft.pex.exe that is installed with VS 2015 RC but when you run it it responds:
launched Pex 14.0.22823.1 x64/IA64 Edition on .NET v4.0.30319
Instrumentation Driver Configuration error: Microsoft.Pex.exe is an internal exe
cution driver and should not be called directly, use pex.exe instead.
But I can't see a pex.exe installed anywhere by 2015 RC

VS 2015 RC doesn't support running pex from command line.

Related

command line MSBuild works - remote build produces errors

I am setting up a process to build remotely a suite of COBOL programs. A virtual machine has Visual Studio 2017 installed along with a Micro Focus COBOL Enterprise Developer 4.0 Visual Studio 2017 plugin. The programs use CICS as their UI and work with a Microsoft SQL Server backend. Opening a developer command prompt in Visual Studio and issuing a MSBuild command with the solution as the parameter successfully builds the programs. A remote build does not - the error is
MSBUILD : error MSB4025: The project file could not be loaded. Root element is missing.
any ideas?
You need to install the "Micro Focus Enterprise Developer Build tools" on the CI machine.

Where can I find Nunit GUI RUNNER for 3.01 and how to run it?

How to run nunit 3 GUI Runner?
After installing NUnit.3.0.1.msi --> I don't see the GUI Runner under
C:\Program Files (x86)\NUnit.org
Where can I find it and how to start GUI?
The GUI runner for NUnit 3 is still under development, version 0.1 is expected to be ready soon.
In the mean time, you can run either with the nunit console. (Or alternatively, within Visual Studio with the NUnit 3 VS Adapter, with you can install as a Visual Studio extension.)

Debugging Typemock test case in Visual Studio 2015 throws TypeMockException

In Visual Studio 2015, when I attempt to debug a test that uses Typemock (and I use the Visual Studio Test Explorer, not Typemock's SmartRunner), on the first call to a Typemock method I get the following exception:
TypeMock.TypeMockException occurred HResult=-2146233088
Message=
*** Typemock Isolator is currently disabled. Enable using
the following:
Within Visual Studio:
Use Typemock Smart Runner
For other runners, Choose Typemock Menu and click "Integrate with Other Runners"
To run Typemock Isolator as part of an automated process you can:
run tests via TMockRunner.exe command line tool
use 'TypeMockStart' tasks for MSBuild or NAnt
I've followed the instructions and verified that:
Typemock is enabled
I already have "Enable Mocking integration" checked in the settings
Also,
The test runs properly when I choose "Run Selected Tests". I only get the exception when I choose "Debug Selected Tests"
Prior to Visual Studio 2015, I did not get this exception during debugging.
Question: What is causing this problem and how do I fix it?
The IntelliTrace functionality does not work with Typemock. Disabling IntelliTrace in the Visual Studio options (Options->IntelliTrace->General->Enable IntelliTrace) works around the issue.
See:
Typemock: Typemock Isolater is not currently enabled
Typemock: Debug Test on 64 bit machine
Typemock: On Windows 7 x64 with VS 2010
Disclaimer: I work at Typemock
This issue is fixed in Isolator 8.3 and will apply to all following versions.
Isolator 8.3 was released on 2.21.2016 and available for download at www.typemock.com.

MSBuild SonarQube Runner: "Failed to locate the code coverage command line tool" still with version 1.0.1

I am trying to use MSBuild SonarQube Runner to have my TFS-builds run the Sonar analysis.
I have configured the tool to work with our sonar Server according to this manual. Actually I can start an analysis by building manually via console on my local machine. Additionally, I installed the tool on our build server and when I run it via Visual Studio, I’ll get the error "Failed to locate the code coverage command line tool".
I already found out that the CodeCoverage.exe is needed, but only given with installing an Enterprise version of Visual Studio on the server. I also read that in version 1.0.1, this issue should be fixed (see here and in the changelog this is also mentioned as fixed).
I exchanged the old MSBuild SonarQube Runner with the version 1.0.1, but with building on the TFS in Visual Studio and adding the command lines to run MSBuild SonarQube Runner v1.0.1, I still get the error "Failed to locate the code coverage command line tool".
I also have Visual Studio 2015 Professional installed on the build mashine.
How can I fix this issue without needing an Enterprise version of Visual Studio providing the CodeCoverage.exe?
Code Coverage still requires Visual Studio Enterprise in the 2015 version (see this page).
The bug you referred to fixed an issue in version 1.0 that meant that analysis would fail if the code coverage tool could not be found. Analysis will no longer fail if the code coverage tool was not found, but it doesn't change the requirement to have to VS Enterprise installed if you want to use the Microsoft code coverage tools.

TestComplete 8 and TFS 2010 Lab Management

I'm tryng to run TestComplete 8 tests with TFS 2010 Lab Management and I keep getting following error when running tests:
File extension specified '.tc8test' is not a valid test extension.
I can't seam to find any solution for this problem.
Did you install TestComplete (with TFS integration modules) on the Test Agent PC, and the PC where you are configuring your tests (where Visual Studio is installed)?