Karate - Robot for Java Based Desktop application. Unable to identify controls using Inspect.exe [duplicate] - karate

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
For those that have used Karate robot for automating desktop applications in Windows written in Swing I'm curious to know what your experience was like? i.e. were the test runs reliable or flaky?
What was the best spy object tool you used to help identify Swing components and feed that to Karate scripts?
Also I see that https://github.com/intuit/karate/projects/3 MacOS support is in the backlog, is there any update on whether this update will support Swing apps on MacOS?
Appreciate your support, thanks.

Developer of Karate Robot here. Most known users are targeting Windows MFC / C++ / .NET or Delphi so there are no reports of Swing yet, but my guess is that it should work at least on Windows. "inspect.exe" works well to introspect the component tree. And we are looking for contributions for Mac, but there doesn't seem to be much interest - yet.
To summarize, I think your best bet is to contribute code to Karate, and you can make that decision based on your comfort with Java and your evaluation of how good Karate is in its current state and if it will "stay around", mature into a good desktop testing tool etc.

Related

"Record and play" tools or "Code/script based" tools? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 months ago.
Improve this question
I am new in test automation.
We are going to plan to start test automation for our platforms (iOS, Android and Web).
I should decide between "Record and Play" tools (eg. Ranorex) or "Code/script based" tools (eg. Selenium) with C# programming.
I have already tried both Ranorex and Selenium, but I cannot decide which tools should I choose.
I would be so grateful, if you could help me to choose the right tools.
Recored and play for e.g. SELENIUM IDE .
Disadvantage :
Works in Mozilla only.
No object orientation.
Advantage :
Record and play option.
Does not require server to start testing.
It has UI.
Core engine is Javascript based.
for this Code/script based we have Selenium webdriver.
Advantage :
Support for multi browser.
API's are entirely object oriented.
Interacts natively with browser applications.
Does not require server to start testing.
Disadvantage :
Does not support record and playback and has No UI.
Conclusion :
It depends on your team, budget, software, and there are n number of factors, but My preference has been code, since once you've the code written you can run that code on multiple browser and on multiple platform. so basically you have more coverage with mere changes.
Based on my own experience and the experience of all the professionals I worked with and spoken with it is much better to work with Code/script based tools like Selenium.
The most "problem" in this approach - you will need engineers with good coding skills to perform this job while to make automation with Record and Play tools you can do with less professional staff.
if you go for ranorex you'll get both:
Selenium WebDriver is built into the Ranorex core
Here you can find a list, comparing selenium vs. ranorex

How to decide which type of testing(Manual or automation) required when we get new web application? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
How to decide which type of testing(Manual or automation) required for a project or application to test?
What are the parameters we have to consider to select which type of testing(Manual or automation) to test very new application?
It depends on :-
Size of the project- If the project is large and consist of so many functionalities then automation testing is suggested
How many times you want to test a particular feature- If the requirement is to test regularly then automation test is best
Font size and image- This can not be tested through any automation tool so to test this, one should need to do manual testing
To find bugs- If one needs to find a lot of bugs, Manual testing is suggested.
You shouldn't have to choose between automation testing and manual testing the way you're asking. The way you're asking it gives me the feeling that the product is already waiting to be tested. In this case you would need to resort to manual testing.
Ideally you would want to have both and even more of automation. Some of the questions that you need to ask are:
Is this a new project or an existing one? If it's a new project then it's easier to plan for automation from the start. You could start implementing automation tests from the start. If it's an existing project then you'll need time to set up automation + write scripts etc. Then you have to resort to manual testing initially.
Is there any existing team? If yes, then what are they doing. You need to continue the process instead of suddenly disrupting it for anyone.
How much resources (money+people) do you have? Do you have manual testing resources? Are they busy or do they have bandwidth? How many automation test resources do you have?
What kind of project is it? Who does it go to? Does it have human lives depending upon it? Does it need a legal certificate of some kind for being tested?
There's just too many questions based on how your question is currently stated. I hope that this answers your question when we consider it generally. But if you're looking for a particular answer then please consider adding more context.

What is the difference between Proctractor and Selenium? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am in the stage to find out what is Selenium. Its website looks very old. Here is a nodejs version of it.
I also found a good in browser testing solution protractor.
Are they designed to do the same thing? Which one should I use? Why Selenium website is so old, out of favor?
All tools you mention above like protractor, nightwatch are all based on selenium. If you are looking for a nodejs based solutions you can either directly use WebDriverJS (popularly known as selenium) or use many other frameworks which are developed on top of it. Every framework below offers unique features, you need to pick what works best for you. The basic advantage of using framworks is that they do most of the heavy lifting for you, that way your code is small and maintainable. UI testing is hard, the smaller the code you have the easier it is to maintain
protractor (good support if your app is angular)
nightwatch
nemo
webdriverio
wd

Why Selenium is becoming more popular than QTP? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Recent stats from job trends:
There is a steady raise in Selenium stats from 2008, birth of Selenium WebDriver in market.
Suggest your views and ideas on this... So that the future generation will learn from you.
It is also fair to say that Selenium is very light-weight and developer-friendly. You can easily integrate with existing unit testing tools in the same language in use by developers. Tests can be executed quickly and provide immediate feedback. You can even run multiple tests concurrently on the same machine, where QTP only lets you run one test at a time.
Lots of reason. To name a few -
Selenium is an OpenSource Tool [Free].
Selenium has a very active community for support and updates.
Selenium gives you freedom of choosing programming language.
Selenium can be used in any OS environment (If I am not wrong QTP is limited to Windows)
You can use selenium with any IDE of your choice.
Large array of drivers (browsers like IE, FF, etc even Android and all)
Again because it is FOSS. Free and very active community.
Every tool has it's pros and cons; And even Selenium has cons. But, what makes it better than QTP is:
Open source
Highly Extensible (Vast varieties of add-ons)
Supports various operating systems
Can run tests across different browsers

Automated UI testing for an Eclipse RCP application [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
What tools are available for record and play back type testing of an Eclipse RCP application?
I'm hoping for something that the end users will be able to pick up pretty easily and record their user acceptance tests with.
Have a look at this:
http://code.google.com/p/robotframework-eclipselibrary/
Robot framework is one of the easier testing tools for end users to pick up as it nicely separates code from tests.
WindowTester supports testing of SWT and Swing applications. It supports recording actions to Java tests. It was developed by Instantiations, which consistently delivered excellent products for Java development, integrated well within the Eclipse IDE. Google acquired Instantiations this year, and now offers WindowTester as free software.
Squish, by FrogLogic, supports many UI toolkits, including SWT. I toyed with the Qt version a few years back, and liked it. Squish supports recording to scripts that you can then edit, in Python, JavaScript, Perl or Tcl. Scripts are not dependent on screen coordinates. On the downside, Squish is exorbitantly priced, and it's licensed per UI platform.
Some other options are described in this previous question.
A comparision which includes most of the tools mentioned in the other answers (WindowTester, Squish, RCPTT, Jubula) can be found directly on the Eclipse website.
This question is quiet old and the answers outdated. RCPTT is a great if not the best solution to this problem. Free of charge and you are able to record user interactions
Eclipse foundation now has Jubula ptojext. See http://eclipse.org/jubula/ "Jubula"