vstest.console.exe open nunit GUI but doesn't run tests - selenium

I have a visual studio project which includes a test with selenium code. I am trying to run this using vstest.console.exe using command
vstest.console.exe C:\Code\SampleReportsProject\SampleReportsProject\bin\Debug\SampleReportsProject.dll
On running this command, it opens NUnit GUI window but doesn't execute the test.
On running again, I get message
Starting test execution, please wait... Warning: No test is available
in C:\Code\SampleReportsProject\SampleReportsProje
ct\bin\Debug\SampleReportsProject.dll. Make sure that installed test
discoverers & executors, platform & framework version settings are
appropriate and try again.

Related

How run test cafe studo tests from command line

Good day.
I want to run the test cafe studio tests from the command line because our CI(TFS) is not supported.
All the examples that I found are intended for the Old version of the test cafe or for the free version.
Thanks.
The open-source TestCafe version can run tests created via the TestCafe Studio in the same way as regular TestCafe test files, so you can use the following command to run tests:
testcafe chrome ./tests/fixture-created-in-tc-studio.testcafe
https://docs.devexpress.com/TestCafeStudio/400610/faq

Running webdriver IEDriver on Jenkins fails

I have a small C# webdriver test suite dll which I recently created...
Runs fine in Visual Studio
Runs from the command line perfectly using the NUnit 3 console runner.
I have Jenkins installed on my laptop (for testing before I put it into my live Jenkins), running with my Windows credentials. When I execute the test suite using the same NUnit3 console runner command I used before, all the tests fail, can't even log in as it can't find any elements. I took screenshots with Selenium & it's just a black rectangle!
Anyone have any ideas on how to get IE behaving - I bet it's a Windows permissions thing from Jenkins. Thanks!
I'll answer my own question.
Turns out you can't do what I'm attempting - it's a known issue with the way IE is built. What I had to do is install a new Jenkins node on another machine and get that to run the IE tests. That way it did work.

When selenium test runs by Jenkins and MSUnit, the browser doesn't come up however there are valid results

I put together a machine (Windows Server 2012R2) for POC reasons where a Jenkins installed and it executes Selenium UI tests using msunit
But, when I log in the server where the Jenkins runs and I watch what happens during CI build (compile and test execution) I can't see that the browser (Firefox) starts automatically, however, the test results and the logs show that a browser was executed.
My question is that, what the is happening when my tests are executed by Jenkins? If I execute the command which from visual studio on the same machine then I can see that Firefox starts, does what is programmed in the tests and the results are in the result.trx.Can I somehow set up Jenkins the way the browser really executed (I can believe it when I see it :)
In Jenkins when you run selenium test cases, they are executed in the background by default.
Your Jenkins might be configured to run those test cases in some video buffer(usually it happens on Linux but can also be configured on Windows) or in a headless state.
As your question, if you are using MSTest which basically used to convert the test cases result from trx to JMX format but also can be used to run selenium tests. when you run the same in Jenkins it will run in background on any slave or on master.

How can I run a Xamarin.UITest from the commandline?

I would like to run tests (made using Xamarin.UITest) on my build server, which runs TeamCity on OS X.
I have searched online on how to do this, but I am only able to find how these tests can be submitted to Xamarin Test Cloud. This is not what I want, I want to run the tests I wrote directly on devices (and/or simulators) connected to the build server.
according to the docs (requires NUnit 2.6.3)
$ mono <path-to>/Nunit-2.6.3/bin/nunit-console.exe <path/to/uitest-assembly.dll>
Here is what I do on OS-X:
Locally install the correct nunit-console.exe version
Build the app
Build the uitests
Run the tests
Example:
nuget install NUnit.Runners -Version 2.6.4
xbuild iOS/UITestFromCmdLine.iOS.csproj /target:Build
xbuild UITests/UITestFromCmdLine.UITests.csproj
mono ./NUnit.Runners.2.6.4/tools/nunit-console.exe UITests/bin/Debug/UITestFromCmdLine.UITests.dll

How to run NCover v1.5.8 & Gallio v3.3 on x64 machine

I'm struggling with NCover v1.5.8 & Gallio v3.3 on x64 machine. It can run all the tests but cannot produce the coverage report. The error message: "Profiled process terminated. Profiler connection not established"
The command line I used:
NCover.Console.exe Gallio.Echo.exe MyTests.dll //reg
I tried to do the same thing as TestDriven.NET can produce the report but I have no idea where to get the "Gallio TestDriven.Net Runner". My expectation is having the coverage report from my MBUnit tests :D.
I also tried to run like this
NGallio.Echo.exe MyTests.dll /runner:NCover
But it then complained about NCover 1.5.8 cannot run at .NET Fx v4.0
Anyone got the same problem?
If you install Gallio (using the msi) and you already have TestDriven installed, it will install the TD.Net runner.