I'm currently working for a client whose request is to make a test automation for a desktop application. And they recommended using cypress.io, which i think was built mainly for web automation. I tried looking to their docs but it seems I can't find anything that enables it to run desktop app automation. Sorry for the noob question, I'm still a newbie here.
Thanks in advance for the answers!
cypress.io is not capable of automating desktop apps.
(Source: Did a brief POC couple of weeks back with Cypress.io)
Cypress is more about a web application automation framework. This means if the application can run in a browser, Cypress can automate it.
Even their GitHub project header says the same :)
https://github.com/cypress-io/cypress
Related
I was working on a ionic mobile hybrid app and looking for automation testing tools. I found Codedui a solution for testing windows/web application and I was wondering if this can be used for testing ionic apps as well. I will appreciate if someone who has done similar task can share his views. Many thanks.
Never hear about Codedui before, but I suggest to use Protractor to test automatically your App. Protractor runs tests against your application running in a real browser, interacting with it as a user would.
I am working in a team responsible for development and maintenance of an enterprise web solution project where the front end customer portal is developed with PHP on Yii framework and backend web application for back office operations is developed with Python on OpenERP.
We are trying to automate the test workflows using only open source test automation tools are looking at options like Selenium,DalekJS.
My question is, keeping my project in mind which tool would be ideal to easily automate test workflows with a great test coverage and easy maintainability. We might have regular enhancements and fixes for both customer portal and back office web application. Which tool would be better keeping my project in mind, is it Selenium or DalekJS?
Any inputs/feedback or past experience would be quite helpful.
Hi Shashi Vardhan Andem,
unfortunatly it seems DalekJS is dead, unmaintained dependencies, last commit 2 years ago. We recently switched from dalekjs to http://webdriver.io/
So to answere your question. Definitly Selenium because it's gonna be still developed.
Cheers,
Dennis
I have two questions about testing a browser
The browser I am trying to test is somewhat hybrid. It sometimes runs in chromium way and sometimes runs in internet explorer way
It's hard to check whether all the websites work well in a browser. How would you check that? If there is a good open-source automation tool to do this, would you guys recommend me?
If there is anyone testing a browser, how do you guys automate the test? (if there is a good scenario form, i'd be grateful if you guys share and sharing a automation tool would be nice too)
I'd appreciate it if I get a reply :-)
https://crossbrowsertesting.com/
http://www.multibrowserviewer.com/
you can use selenium ide tool for automation testing.
There are a few good technologies in this realm:
For testing and validation of web development / websites in general you can use Selenium Grid which is meant to test websites in various browses
The URL for Selenium Grid: https://code.google.com/p/selenium/wiki/Grid2
To automate use cases in a browser you can use the free popular Selenium tool which can be used in various languages (http://www.seleniumhq.org/download/).
Other tools:
Mechanize (http://wwwsearch.sourceforge.net/mechanize/)
Watir (http://watir.com/)
Forgive me for what may seem as a stupid question but, after some rummaging around on the web, I can't seem to find how to test my Windows Phone Application. I'm not referring to the guidelines, I'm actually referring to sending it to Microsoft for them to check if it's "okay" or checking it on Visual Studio as I think there is a way of doing that in VS.
Any help is highly appreciated.
Thank you.
This should help. Keep in mind that before you send it to microsoft (or appHub) your app needs to be fairly perfect. Submissions aren't free :)
edit: this is assuming you were asking how to submit it for review. When you submit your app, the review process starts.
For app testing you need the sdk... With the sdk you have a perfect emulator for test your apps. For app deploy on your device, after you've bougth the annual subscription to be a developer, you have to associate your phone and install zune on your pc (read here).
After you tests you can submit your app through this process (read here).
I am about to start work on a UI automation project for a client who is using Siebel 7.5. I have been looking around and it seems that there is not a lot of info out there on if it is possible to automate GUI tests in siebel using Selenium. The question is, Is it possible to automate Siebel using selenium. I hear there are two modes for Siebel, SI and HI, what is the difference?
On another note, i have heard that there are issues automating early versions of Siebel using HP QTP. What are these issues and what is the best workaround.
I realise this is more than one question, i will vote up whoever answers a component and the answer will go to the person who answers the most components
Thanks in advance
HI stands for "Hi Interactivity" it is used for sites that are accessed over the LAN most objects in an HI Siebel application are ActiveX controls.
SI stands for "Standard Interactivity" it is used for sites that are accessed externally and is usually pure HTML.
Starting in version 7.7 Siebel starter supplying Siebel Test Automation (STA) which provides an API for testing tools, this API is used by QTP for testing Siebel 7.7 and later. STA is relevant only for HI applications, for SI applications Siebel adds some hints to the HTML in order to help testing tools.
I don't know of specific problems with QTP testing classic (pre 7.7) Siebel applications and I don't know about Selenium at all so I hope the general information I provided is useful.
As said above, HI mode can have test hooks enabled but these are pretty basic and need some additional software to work with easily. Also, HI only works in IE which does not have the great Selenium recording tool.
On the other hand, SI mode is just HTML and works in Firefox, therefore should be testable with Selenium. Does require a little set-up and please bear in mind that there will be differences between the test results for SI and what the users will see in the much-more-usable HI mode - but if you can ignore the use of special applets, and avoid client-side coding, it should work.
You could use a combination of Ruby watir-classic and rautomation plus a bit of javascript to interact with almost all of the Siebel HI Components. The two Ruby gems use WIN32OLE API and COM, so in essence you could use any language that supports the Windows API. It's a huge effort, but pays off in the end, cause it's all open source, whereas tools like QTP and TestComplete cost a fortune.