Perhaps a bit of a dim question, but here goes. Can TestCafe Studio be used to create tests for Electron based apps? Having played with it a little, I can see no clear way to do this, and it only offers the usual browsers. Is this a bit too niche? I understand that open-source TestCafe itself is capable of this, but I'm demoing Studio to see if it's suitable for someone who has little experience.
Currently, TestCafe Studio does not support recording tests for Electron applications. We will consider this functionality as a possible enhancement for our future updates.
Related
My team is currently starting to develop a web application with vue.js. We are currently discussing the test framework and a team member prefers cypress. The only issue is, that cypress is not cross platform testing framework. We have requirements to support Chrome, Safari, Edge, tablet and mobile devices.
Most of the modern frameworks such as vuejs promise cross platform functionality. And the raised discussion that we had in the team is the need of cross platform testing. Is it still so important in 2018(almost 2019) to do cross browser and cross OS Platform tests? What do you use for testing and how do you test your web application?
Thank you in advance for your answers.
Of cource the alternative is Selenium using selenium wrappers like Protractor or Webdriver.io or Nightwatch.js.
For same reason, we are not using Cypress. We are using Nightwatch.js. Coz in the above list of wrappers it only has everything inbuilt like cypress. For others in the list we have to find the respective npm for test runner, assertion reporting, parallelisation, etc.
Mainly we have choosed it for internal test runner and junit xml reporting for ci which it gives along with selenium wrapping functionality.
Also one more good thing cypress is working on cross browser support. Recently they have progress in firefox browser.
Refer this issue tracker
We have this same dilemma at my organization. I find Cypress so easy to use that I am ok using it for 99% of my test (that does not include my unit or api test). If I need something special for another browser, which is probably going to be minimal, I would then use a selenium wrapper, for me that would be protractor since we mainly do Angular. I hear a lot of argument not to choose cypress due to the issue that it currently only runs in Chrome, I think sometimes it is an excuse for someone to hate it because they don't want to learn something new. I would bet 90% or more of your test cases Cypress will be just fine, where I need something else I do something else. When I look at the testing triangle, I know most of my test should be UNIT test so I don't have enough UI automation test to worry about it. I will say I have ran into this same argument at my job from developers who say why don't use protractor, and they have the freedom to use protractor, but I notice they never get around to using it. They like to argue about what someone else wants to do, but then they don't even use what they say they prefer. I would ask myself what is going to be the cheapest to implement and be the most effective for me. For me that is mainly cypress and then protractor if I have some special case..
Im looking for some alternatives for Coded UI test. Unfortunately I'm only running Visual Studio 2013 professional
I have already looked at Selenium for Firefox, but that does not seem to work in my version of Firefox
If you want to test web applications, you can use any of the following:
Selenium
Cypress.io
Nightwatch.js(uses Selenium BTS)
For Windows desktop applications, Microsoft is now supporting Appium based WinAppDriver. For more details, you may check the GitHub repository here. I also teach a Udemy course on the subject which can be seen hereenter link description here.
White is another desktop application testing API but I haven't used it a lot.
We previously used WebAii to test a complex ASP.NET application and it was successful. I have found out that it is now part of Telerik controls. (I have no affiliation with the company.)
http://www.telerik.com/videos/details/teststudio/webaii-testing-framework-and-nunit
Other than that, keeping the UI as light/dummy as possible and testing beneath it extensively usually worked out better for me.
Does anybody have a recommendation for unit testing home grown rally apps?
I've started to look at Jasmine as recommended in the Sencha docs and it looks promising, but I'm a little unsure about how to tie in all the Rally infrastructure, and I'm not a Javascript expert.
If anybody has used Jasmine for this, do you have some examples of how to set up a basic configuration for using Jasmine to test a SDK2 Rally app?
One of the next things I wanted to create in my app building framework was a tie to some testing framework. I was leaning towards Zombie, you may want to check that one out.
Has anyone used QUnit to test Windows Store App? Any recommendations on how to run testing smoothly? I seem to be having issues stubbing methods that cite some of the internal Windows. references. Is there a way to run QUnit while the metro app is actually running, instead of writing tests in a standalone fashion?
Check out this project started recently that helps you use QUnit in Metro apps
QUnit-Metro
There are two QunitMetro libraries available
Codeplex http://qunitmetro.github.com/QUnitMetro/
MSDN Code Gallery http://visualstudiogallery.msdn.microsoft.com/9a49206d-8b60-4324-a23f-eb01264ece3d
I recommend the CodePlex version as I have not tried the MSDN one.
I am wondering what tool(s) do you use for front-end testing...
Currently I am using Selenium RC as tool to test the front-end. I am quite happy with the result as I managed to integrate it with the ms build process etc. The problem with Selenium tests is that they are not always reliable especially if you browse with something else than Firefox.
I am looking for open source alternatives (tools for front-end testing)?
I'd recommend TestPlan which can use Selenium as a backend, or HTMLUnit. It also allows you to do a myriad of other testing. It also works around several of the problems Selenium has, making it a bit easier to user than Selenium directly.
My experience shows, Selenium works the best from everything I tried. Even now I work with Firefox 6 and Selenium IDE works perfectly with it.
Together with selenium, we're also using twill. However, it is because of its speed and it is used only for "quick & fast" tests, I'm afraid not a lot of things are better then selenium out there.
On the other hand, I find Selenium quite reliable, even in another browsers - it's just hard to build tests in such way, to think about race conditions etc.
Have you heard of Watin ?
There is a great tool named cypress.
With cypress it is possible to write
End-to-end tests, Integration tests & Unit tests.
It is open source.
Learning curve is very low.
https://docs.cypress.io/guides/overview/why-cypress