I'm trying to figure out if there is compatibility between test cases written in TestCafé Studio and TestCafé open-source.
The major difference is that open source only has the command line interface, but I suppose that a test case created with visual aid in TestCafé Studio still has some underlying code that is executable as command line in the open source version?
There is some more info here: https://community.devexpress.com/blogs/aspnet/archive/2016/10/18/testcafe-now-available-in-free-open-source-amp-commercial-studio-versions.aspx and here https://devexpress.github.io/testcafe/faq/#what-is-the-difference-between-testcafe-studio-and-open-source-testcafe
You can run TestCafe Studio tests (.testcafe files) using TestCafe CLI. For more information refer to our CLI documentation
Related
How can I execute a test via command in a way that the test run is shown with all its results in TestCafé Studio afterwards?
I'm using:
npx testcafe [browser] [TestCafe file]
The test is executed but the results are only visible in the console. Is there a way to fully integrate it in TestCafé Studio?
BTW: Why isn't there a tag for [testcafestudio] – the product is not that new ;-)
EDIT: I'll take a little further out: We would like to switch from TestCafé to TestCafé Studio to increase the number of people who can maintain and create individual tests in QA. Some tasks could then also be handled by employees with somewhat lower HTML skills. In addition, we would like to keep the connections we are used to, so that the tests are still triggered at certain times or manually via a Jenkins pipeline (Jenkins-->VIX-->CMD-->TestCafé Studio). Depending on the configuration of the respective test run, different branches would be used for the TestCafé Studio project via Git. The test results are read, parsed, and written to a database after the test run is complete. In addition, I would like to see the atomatically triggered calls available in TestCafé Studio, as it is very convenient to navigate directly to the failed tests.
Is it not yet possible to start tests in TestCafé Studio via CMD?
TestCafe Studio stores reports in its own format while TestCafe stores reports in various different formats that are inconsistent with the IDE format.
You can run tests in the TestCafe Studio itself. Are you running your tests in CI? If so, what CI are you using and why does not its reporting system meet your requirements? If not, could you please clarify why you are required to run tests outside the TestCafe Studio IDE?
I have some tests for a web application which were automated using SpecFlow and Selenium WebDriver. When I run the test from Visual Studio's Test Explorer, the test runs fine. I'm trying to set up a CI pipeline on Jenkins and in order to run the automated tests I'm relying on vstest.console.exe. However when I run the from the command prompt using vstest.console.exe, the application didn't appear as it should. When I checked the Console in Chrome's Developer Tools, there were a quite a lot of js and css files logged as Internal Server Error. Below is a screenshot of the console error for a few files.
Any help with this will be greatly appreciated...
So I have a JMeter load test that is running in VSTS. I was wondering if it is at all possible to run this test through Visual Studio itself? I would be interested in viewing more details about the test through Application Insights.
The JMeter test is running in the cloud. I know about load test projects in Visual Studio, but is there a way to add the JMeter tests from VSTS?
Many thanks.
It is not supported to add/run Apache JMeter load test through VS 2017.
There are many ways to run JMeter test: Five Ways To Launch a JMeter Test without Using the JMeter GUI.
You can try to create a test adapter and call test through command line. How to create and install test adapter in Visual Studio
Has anyone successfully used the MSpec Test Adapter with TFS? If yes, can you please shed some light on how I would go on about doing this?
I noticed this post but it uses the console runner.
After lots of research and trial and error, I finally figured how to make this work. It's actually pretty easy.
Install the MSpec Test Adapter on the build server.
Download the MSpec Test Adapter and change the file type to .zip
Extract the files to a folder on your build server.
Point the "Version control path to custom assemblies" to the files in step 3 above. *Note: You can access the window to do this from Visual Studio by clicking Build > Manage Build Controllers > and selecting the controller.
Ensure in the build definition, you select Visual Studio Test Runner. This can be accessed from the test definition > Process tab > Test > Automated tests > Test source
When you run your build, you should see your tests run.
I'm new to testing and currently trying to write some tests in Android Studio. I have a sample application module and now trying to figure out, whether the instrumentation test needs to be a module of its own or whether the tests should go inside the src folder... I have read contradicting information on the web. If anyone had a sample, that would be great!
With eclipse ADT plugin and older version of the SDK it was a requirement to put the integration tests in a separate module.
With the gradle build system and android-studio you should be able to put your integration tests in src/test/java and running them from the IDE or gradle command line without pain.
That's why you find contradicting information on the web.
Here is the reference
This post contains a very good explanantion on how to do the integration testing in Android Studio:
How can I create tests in Android Studio?