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.)
Related
Environment is
1. Visual Studio 2017
2. Visual Studio Team server
In My requirement is, If i update "TEST SCRIPTS" code in Visual Studio Team server its will build automatically every release. But i need to to RUN the updated "TEST SCRIPTS" in Visual Studio Team server.
There are many tasks to run test, such as Visual Studio Test, Maven Test, Run Functional Test. So you can create a unit test/coded UI test project in VS 2017 and run the test through Visual Studio Test task.
Related article: Get started with continuous testing.
I recommend you run the test during the build.
Regarding run the test once the Test Script code be changed, you can setup a CI build (Triggers tab). If you want to do test in release, you need to publish artifact (test project build result), and configure release with Continuous Deployment mode (Triggers)
Our team is about to start a project using visual studio.net. We haven't decided about solution manager yet.
One of most important parts of our project is Testing. I have worked with TFS before and I know it's so powerful in testing (Link). I don't have any idea how Teamcity deals with different type of testing. May you please let me know about your experience and point of view?
Thanks
This question (CruiseControl [.Net] vs TeamCity for continuous integration? ) has a lot of good answers about TeamCity. It does not only talking about test and do the compare to TFS, but it might shed some light on TeamCity for you.
TeamCity directly supports the following testing frameworks:
JUnit and TestNG for the following runners:
Ant (when tests are run by the junit and testng tasks directly within the script, TeamCity reports tests on the fly)
Maven2 (when tests are run by Maven Surefire plugin or Maven Failsafe plugin, tests reporting occurs after each module test run
finish)
IntelliJ IDEA project (when run with appropriate IDEA run configurations)
NUnit for the following runners:
The NAnt (nunit2 task)
The MSBuild (NUnit community or NUnitTeamCity tasks)
Microsoft Visual Studio Solution runners (2003, 2005, 2008, 2010, 2012, 2013, and since Teamcity 9.1. Visual Studio 2015)
Any runner provided TeamCity Addin for NUnit is installed
MSTest 2005, 2008, 2010, 2012, 2013 and since Teamcity 9.1. MSTest 2015 (On-the-fly reporting is not available due to MSTest
limitations)
VSTest 2012, 2013, 2015
MSpec
You can even custom Testing Frameworks if there is no TeamCity support yet for your testing framework, more details please refer the official documentation from Teamcity: Testing Frameworks
For test in TFS. TFS itself won't shipped with Test Automation tools. TFS use Microsoft Test Manager, a separate Team Foundation client, lets you manage and execute test cases and create and manage physical or virtual environments. It installs with select Visual Studio editions.More info please see my answer in this Test Automation tools shipped with Visual Studio 2015 Enterprise?
As for which one is better, it's hard to say.It still depends on the actual situation of your team. There are many factors affecting this such as: staff's knowledge structure, financial budget, test environment, training of develop tools and so on.
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.
After upgrading both Team Foundation Server and Visual Studio from 2013 update 4 to 2015, i created a build in the new build system.
The build includes only two steps: One Visual Studio Build step and one Visual Studio Test step. There's only one single simple solution with a class library project and a test project.
The Build step runs fine. The Test step does nothing. It just says
Starting test execution, please wait...
but the test are not running.
When i edit the VS Test step in the build definition and set the VSTest version to "Visual Studio 2013" instead of "Visual Studio 2015", everything works fine and it outputs as expected:
Starting test execution, please wait...
Passed <nameoftest1>
Passed <nameoftest2>
Passed <nameoftest3>
Passed <nameoftest4>
etc
I found out that during that build step, the following line gets executed:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe "C:\pathToTestDll\TestProject.dll
So i tried to run this from commandline on my own pc, and found out that when i use vstest.console.exe from the Visual Studio 12.0 folder, everything works fine, but when i use vstest.console from the Visual Studio 14.0 folder, the tests are not running.
I also found out that when i run the command prompt as administrator, it runs all the tests with vstest.console from the Visual Studio 14.0 folder.
Has anybody also had this issue, or is there a way to run the whole build (or just the test step) with elevated rights, so i can run my tests with the VSTest Version set to Visual Studio 2015?
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)?