EPISODE 102: Test Automation with Ranorex [PODCAST]

Ranorex Test Talks
Automation Guild Online Conference Top ad

Test Automation with Ranorex


Welcome to Episode 102 TestTalks. In this episode we'll discuss how using Ranorex for your test automation might be the right choice for your testing efforts with Roland Enzinger, a product manager at Ranorex, and Christoph Preschern, Head of Sales at Ranorex.

Ranorex Test Talks

There is nothing worse than choosing a test tool at random, or using a popular tool just because everyone else is using it. Companies are different and have different needs – so what might be the perfect tool for one team may not mean it’s the perfect tools for yours. So what do you do? My approach is to truly understand the needs and skill sets of your team before making a hasty choice for your test tool selection.


That’s why I love speaking with test tool vendors; I like knowing all the different test tool options in the market as well as the pros and cons of choosing one over the other. In this episode you’ll discover what the benefits of using Ranorex for your test automation are, as well as why or why not it would be a good option for your team.

Listen to the Audio

In this episode, you'll discover:

  • What is Ranorex
  • Does record and playback have any value?
  • How Ranorex fits into Agile DevOP best practices?
  • Tips to improve your test automation efforts
  • How to help teams that are just starting out with test automation
  • Much, much more!

Want to Test Talk?

If you have a question, comment, thought or concern, you can do so by clicking here. I'd love to hear from you.

How to Get Promoted on the Show and Increase your Karma

Subscribe to the show in iTunes and give us a rating and review. Make sure you put your real name and website in the text of the review itself. We will definitely mention you on this show.

We are also on Stitcher.com so if you prefer Stitcher, please subscribe there.

Read the Full Transcript


Joe:Hey guys welcome to TestTalks

 

Roland:Hello.

 

Christopher:Hello Joe.

 

Joe:It's great to have you guys on the show, before we get into it can you just tell us a bit more about yourselves?

 

Roland:Sure. If I may start, my name is Roland, I'm the product manager here at Ranorex.

 

Christopher:My name is Christopher, I'm responsible for sales and customer carrier at Ranorex. I'm with Ranorex since the very beginning. I was in the past a couple times in contact with our customers and I'm still in contact with them. I'm happy to be part of this interview.

 

Joe:Awesome. What is Ranorex for people who don't know?

 

Christopher:What is Ranorex? Ranorex is a functional test automation tool which is driven through the user interface. You can automate anything when it comes to web applications, mobile applications or desktop based applications.

 

Joe:Cool. What technology does it use? Is it image based? Can you program it using a developer tool like C-sharp or Java? How does it work?

 

Roland:It's object based. It means that it recognizes the object itself. You have opportunity to switch to image based as well but this is more an exception than the rule. You can in background, use coding environment so you can use the .NET Framework. You can access it, you can use C-sharp VP dot net but only If you want. We have a lot of tools with a nice URA and the wizard driven techniques to support testers that are not so close to the programming. It prefer other tools but with Ranorex you have the possibility to do both coding or recording, editing and playing back some actions.

 

Joe:You started in 2007, I know there are some major vendors out there already so why create Ranorex? What makes Ranorex different? What's the sweet spot you think that someone would really get benefit from a product like this?

 

Christopher:From the very first beginning it was always the idea to provide a tool which is accepted not only by testers but also by development teams. What we have recognized, especially in the year 2006, 07 and 08 that at this time only the big players have been on board or have offered tools for mainly testers, not so much for agile development teams. The nice thing with Ranorex, is that from the very beginning Ranorex offered a test automation API. From the very beginning there was no tool available you can use, there was just a library which you can use from a developer's perspective. At the same time, we knew that it is important to offer something which is easier to access from more testers’ perspective.

 

It's not the way other tool vendors do. Many other tool vendors they have their test automation designer tool or something like that and then they offer an API in order to make the scripts in the background more flexible. We offered that API from the very first beginning but today I can say that even testers having no programming skills are able to work within Ranorex studios and they can collaborate with their development team which is really useful in times like these when you have more and more agile teams.

 

Joe:Chris you just mention the API, so this API makes it accessible from a different types of tools, so if I had a developer working in their development environment using eclipse or visual studio, they're still able to work with the tool using the API? Or they're able to … How does the API work in that particular situation?

 

Christopher:The API is fully based on the .NET Framework, even within eclipse it's possible to have your own wrapper so you can use core functionalities or object identification mechanism for automation on the API level. Also within Microsoft visual studio it's pretty easy to add Ranorex's core APIs to a specific solution or project in order to do simple scripting within visual studio if you like.

 

Joe:Great, so much comes from 2007. Some of the issues out there I guess continues integration was probably coming more popular and so right out of the pocket, it sound like you have API and because of that, you have that API you could pretty much integrate Ranorex with anything like any continuous integration products. Is that correct?

 

Roland:That's absolutely correct. What results out of Ranorex project or solution that you have is an executable file and every tool that is out there, every continuous integration tool, it's pretty much possible to run command line tools, to run executable files and therefore integration is quite easy. You can run your tests as a build step of continuous integration tools and therefore have the automated tests executed right after your build or in the weekly build or in the night build or whatever so it's pretty much flexible.

 

Joe:Just had an idea here, that executed file … I love this concept and let me make sure I understand it. Say I have someone that's not really an automation engineer, it's a business user. I have like maybe high level test suite that I want them to run. Could I just give them this executable and they can just double click on it and that's all they need to do to run the test?

 

Roland:That's pretty much it. You need some additional files maybe for test data that you wanted to deploy with but in general it's one file that you can double click it and it runs.

 

Joe:Very cool. Do you have any examples of what your customers are currently using Ranorex for? Any problems you know your customers were having before Ranorex and once they got Ranorex they were able to solve it?

 

Christopher:Good question. Usually many of our customers, let's say when we go back to year 2009 or 2010 we recognize a couple of customers which were really unhappy with their existing test automation tool because, in certain situations their tool did not support a certain technology. Think about flash or FLAC based applications, there was a huge amount of this type of a test automation when it came to flash or FLAC based applications and Ranorex was the first tool providing support for this type of application. This was kind of the starting point in many different types of our customer base. They started with Ranorex and then it turned out that Ranorex is also good to use for desktop applications but also for web based applications and mobile as well and many of our customers have a mixture of different types of technologies.

 

One of our key USPs out there is the broad support of the different technologies. Think about .Net based applications but also think about Java based application, think about ASAP oracle forms mobile applications. You have native ones, you have hybrid ones, you have mobile web applications. Everything you could think of when you think about applications. A good thing with Ranorex is that you can combine all these technologies within one test. I always use a good example because many of our customers are doing that and to end test automation. Think about an organization like Amazon, think about such a bookstore for instance. What you can do with Ranorex is easily simulate adding a book to your ERP system   like ASAP.

 

The next step you can assimilate a user looking for the book on a mobile device and adding the book to the wish list. On the next step you can simulate the user sitting in front of the computer and purchasing the book through the web page. Finally you can double check whether the book was removed from ERP system from ASAP. Scenarios like these, you can easily cover within one single test case with Ranorex.

 

Joe:How does a test automation engineer create their test scripts? Is it a keyword driven or do they on develop methods and they just call those methods? What's the language that's used within the Ranorex IDE?

 

Roland:Well the good thing about Ranorex is that you can choose whatever fits best to your needs, to the needs of your team. On the one hand we have tools like a recorder where it can start from scratch. You click the record button, then you click your application and stop the recording and it can replay right away. You can also modify it's in terms of copy paste or format to click elsewhere or changing the [valid 00:08:46] that you typed in. This is for people not being familiar with coding for example or more familiar with tools like excel. Because you have a table and every action is in one row and you can understand it easily. That's the approach a lot of people use when they start with Ranorex.

 

On the other hand we have the development approach where it can do your own code modules, you can maybe extend your existing recordings or if you will can also script one whole thing, a bunch of actions only on code. This is for example, done in chart develop or visual basic .Net where you do your loopings, where do your conditions based on anything that comes from the UI. Also react to things that you see or a based on test data that comes from outside driving a test. It's not the keyboard driven approach it's more of the other thing, that you start your test, you can do data driven tests of course. If you want you can also do a keyword driven approach with another tool maybe that drives the test.

 

Even within Ranorex there's a possibility to do key word driven test if you set up your test like that, supporting that. You can have people that implement function methods that can be used as framework from other people not being able to write their own methods for example. Whatever you want to do with your team, whatever the teams’ skills allow let's say this way you can do with Ranorex.

 

Joe:Awesome. Sounds very flexible and like I said it I haven't tried it myself but I heard from other people that have and all the more we see that it's easy to use and I don't know what that means. Why do you think a lot of customers say that your product is easy to use?

 

Christopher:I think this is because of Ranorex recorder. When you think about capture replay in general, a lot of people out there really have a negative impression about capturing replay and that's true so capture replay has its limitations. On the other hand what we see out there especially within agile teams that automated test scripts or automated tests have to be provided much, much earlier during the development process. There is more and more need at the end for quick automated test scripts. The very first step with Ranorex is the recorder but in addition what has to be mentioned here is that the recorder itself is kind of an action table which you can easily create by drag and drop and click and go.

 

Also when it comes to object identification we have our spy tool which uses in the background Ranorex path. It's kind of an XPath and expression but it's pretty easy to use so that no one really needs to understand the syntax of XPath. The spy editor assist you with different types of mechanism when it comes to object identification. When you want to use regular expression that's possible by just simply using the UI there without understanding the Xpath. That's the main reason why our tool is easy to use and also that the time when it comes to get started with Ranorex and   then the time when you are productive is very short.

 

Joe:Awesome. I just want to reiterate, we're not of saying recording playback is the way to go but it's a good place to start maybe [crimming 00:12:20] a shell of a script because you have to go in and edit it.

 

Christopher:Exactly.

 

Joe:It gives you the ability to at least get the high level structure in place and then you can go in and modify.

 

Roland:Absolutely, people often start with the record to get the idea, to see how it works, they love to use it so when they're more experienced. They somehow extend their own scripts or their own and recordings and test cases with some more advanced if they want depending on the skills that you have in a team you can do multiple ways.

 

Christopher:Exactly, and also when it comes to usability or when it comes to simplicity the great thing here is that even if you could start with the recorder, you quickly realize that you need to split up a recording into smaller pieces. You can say that these pieces are key words for instance. We have our modules and these modules are kind of keywords which you can use to create your own test automation framework, which is easy to use for other people in the team as Roland mentioned before. I think this is kind of the simplicity which Ranorex offers as well. As soon as someone has provided robust test automation building blocks for others. Others can really easy use them from Ranorex's studio perspective, from building a test with respective.

 

Joe:Great. I like [inaudible 00:13:45] playback because I throw them away but I like to use it when I'm exploring a new application just to see whether it recognizes, whether it doesn't. It can be helpful in that regard also. How do you handle object recognition issues? A lot of times, no matter what automation tool it is, you may an application has a custom object that for some reason your application or your tool, that the test tool just does not recognize. Do you any tips for those types of situations? How do you handle in Ranorex type of world?

 

Roland:Well first of all we are very happy to not coming to this situation very often just because we have a varied approach, a range of technologies we support. For exceptions where you have any technology that is not recognized there are some workarounds. Some workarounds are or let's name, one these workarounds which is image based it can also be used for example, because this doesn't necessarily mean that you have to recognize the object itself but you can do it based on pixels on graphic information.

 

That's one way but they're still another way where you can switch on something from the background that doesn't matter type of object recognition. It's our choker, if we can name it this way, that also supports object recognition even it if the technology itself is not supported were [inaudible 00:15:05]. In general these are only exceptions in my opinion. The workarounds that we have, really helped a lot of people.

 

Christopher:If I may add something here, I think one of the major challenges out there is dealing with a dynamic user interfaces. This is a topic which is pretty much very popular when it comes to testing of web based applications. Content which is loaded, every let's say five seconds on the web page. Ranorex has a good ways and good approaches to support this type of object identification challenges. What we have here is that we can or the user can teach Ranorex how to identify objects so there is a rule editor where you can tell Ranorex, “Hey listen Ranorex, do not use this certain ID because this ID is generated on a dynamic basis.”

 

You can use these rules in order to prevent your recordings afterwards from failing when rerunning a test. I think this is one of the key things here and also the combination of XPath helps you to identify things based on attributes from a parent object, for instance. There are certain types of ways to do that and honestly this is one of our major tasks here at Ranorex to assist people dealing with a difficult UI or new technologies popping up out there. First we tried to support these technologies like we did work for cube based applications two years ago for instance. Also when it comes to our older legacy based applications based on Win 32, we still support those applications and even more we implement new object identification methods in order to identify those type of certain controls as well.

 

Joe:I know you handle a broad range of technologies but this one bought your product do they after … When they start testing the application they go, “Oh my gosh I forgot I have to test of your PF. That's another charge. Oh I forgot that I need a test a SAP, that's another charge.” How does that work with Ranorex?

 

Christopher:The nice thing with Ranorex is that you have everything within one license so there is no extra fee you have to pay just because of a new technology. Everything's included out of the box. The reason why we decided to do it this way is that, we know that in these days that our customers are switching much faster to newer technologies compared to 10 years ago. We have everything within one package and one price and that makes life a lot easier for our customers.

 

Joe:Awesome. Now I know in my own instances a lot of vendor based test tool haters out there. Would you say to someone that says, “Why do I need a vendor base tool? I can you Selenium as a coolant and I can create my own framework.” What would you say to someone that brings up that particular objection to buying a vendor based tool?

 

Christopher:It's a valid point. We have these discussions with our customers as well as what we see is that especially those free tools or open source tools like Selenium are more, more popular and it's okay, those customers are using those tools. What we see quite often is that people are starting with test automation, they're starting with Selenium. Maybe not only starting as a on the strategic basis. They are not the thinking about how to roll out a test automation framework within the organization. The thing with the Selenium, when you compare a vendor based with Selenium for instance, one big thing is that you have to invest first into your automation framework.

 

If you go with Ranorex for instance, you already have the base of your framework, you already have a solution for managing your objects for managing your repositories, which at the end helps you to keep maintenance low. Also what you have are converted to Selenium is a great support. Right now Ranorex has a forum with more than 25000 users. The community's really great here and also when it comes to tooling. There are a lot of features included and also especially when you talk about Selenium you always have the limitation on web.

 

With Ranorex you can combine tests going across multiple technologies. Think about a dialog popping up in Firefox for instance, which is driven by the browser itself. How to deal with that when using Selenium and also who's giving you to guarantee for the code you have downloaded from the internet, whether this works or not? The biggest challenge in my opinion is that finding the right people being able to use Selenium. Being able to implement a [robust 00:20:12] test automation framework. Based on that framework for sure you can involve others in your team but you need the rights team, you need the right players in the team in order to be successful with Selenium.

 

Roland:When you're only compare the price of the tool, of course, a free tool it's kind of obvious to take it. If you count further and see what costs additionally come in like you need to set up the framework you don't have any support that helps you or that brings you the results and then the answer that you need to right now. Then of course it needs more time and this means more costs to. At the end of the day if you compare it again I really think that people can be happier using Ranorex then with some of the free tools out there.

 

Joe:I agree. I know a lot of people who disagree with me but I'm involved with hiring and finding someone that has the skills to create Selenium from a developer's perspective is very, very difficult. I see where vendor tools can come in and help give that the scaffolding for a framework where we do have to reinvent the wheel. It comes in with built in reporting and built in object repositories which is a big help in objects spies all built into the tool. Big, big help. You know how to create your own framework from scratch, [inaudible 00:21:34]you don't have junior developers trying to be real developers that really are going to mess things up anyway.

 

I've seen I seen horror stories with this so I guess my question is though … Because of this I've seen more vendors like HP came up with a tool called Lean FT which basically you can write test automation with inventors languages and ideas. Also I think so Smart pick came up with something called [Tess left sim 00:21:54] concept and also they both work Selenium. Does Ranorex work with Selenium? Is that something where they, someone [inaudible 00:22:00] task flow where said they had existing test Ranorex and Selenium they realize, “Oh my gosh you know what? We want to leverage these tests and not forget about them when the leverage we have a ready but maybe we do need a vendor based tools, maybe help with the object recognition and object repository type stuff.” Do you work with Selenium?

 

Christopher:Usually it's possible with Ranorex to trigger any type of other tool from the Ranorex's perspective. You can you can trigger other test, you can also trigger a Selenium scripts from a Ranorex test suite so that's not a problem at all. You mentioned LeanFT or test left from smart test complete. What we see here is and this is right thing with Ranorex, we already provided this way of doing automation and agile team from the very first day. The very first beginning we just offered as C plus, plus based DLL for instance, which was easy to use within software development life cycle.

 

Even today you can work with the code, you can broke with the DXC but you can also introduce Ranorex to your DevApp for instance, so that they can easily integrate it into their continuous integration framework. Yes, I mean that’s the nice thing with Ranorex, you have the pure flexibility if you want to trigger a web service based test you can do that. If you want to use OPI for that you can trigger them from Ranorex perspective. Because of the fact that everything is based on code in the background, you have .Net and you can do anything from that perspective. Even if you want to double check database, whether that database has a certain time stamp or something like that or an updated record set you can do this from Ranorex.

 

Joe:I'm going to take it up a little higher level now. I'm always curious when I speak with test tool vendors to know how do you actually test Ranorex. Do you use Ranorex to test Ranorex? How do you trust in house?

 

Roland:Well, yes we do test Ranorex using Ranorex but not only of course, we have a test automation framework that is based around Ranorex. Besides that, there's a couple of other tools supporting the QA in their daily and weekly analyzation. That works out pretty well and it gives us also the opportunity to gather early feedback from our intelligence because they are using our tool all day long and they know how to use it. That's why it’s kind of useful for us internally as well.

 

Joe:Also you mentioned are agile a few times that Ranorex really was created in 2007. It seemed like it was created just for the explosion of agile, in automation of agile. Do you have any best practice in general how to implement test automation in an agile environment or an agile team?

 

Christopher:It is important that you consider that test automation is an important part within your agile team. Think about 7 people working in this team and think about who should get started with test automation there. For sure those type of team players having more testing experience they should think about which test cases are most important for regression testing. Our recommendation here is to say, “Okay think about those test cases which deliver quick feedback for developers.” Even in a situation where you think about, “Okay I don't have a stable software right now. I'm not sure whether I should take it started with an automation task.”

 

Even in these situation it’s useful to use for instance, the Ranorex recorder even though when you have a situation you can throw away this recording or this recorded test script 2 weeks later. As long as this recording was stable for let’s say 3 or 4 days delivering quick feedback to developers. It was good enough. On the other hand I always say to our customers or we recommend that think about having one team player being responsible of creating a robust regression tests suite you can use on a daily basis. There might be a couple of unstable tests, created with the recorder but this person should really think about it, “Okay, what should be used for my regression test suite which I can use on a daily basis.”   This way a test automation framework should grow so that framework is able to deliver quick feedback from a daily build perspective.

 

Roland:The good thing with HL teams or Intel environments. Yes that you sometimes or usually have environments that you source control already, that have continues integration already, that might also be implementing their own application based on the .NET Framework. Even if there's another frame but you have some tools available. That's why Ranorex perfectly fits into this chain of tools because it supports the agile process from the very beginning as it integrate all the tools that are available and supports whole work flow.

 

Joe:Awesome. This remind me of an issue I had previously with another vendor based tool where did integrate with our version control. Does Ranorex integrate with any version control out of the box? Like I can just checked in my scripts into version control and I have to worry about anything?

 

Christopher:From an integrated perspective Ranorex studio get supports sub version and team foundation server. The nice thing with the Ranorex studio project structure is that everything is file based. Even if you have the situation that Ranorex is not supporting your version control system, within Ranorex studio you can always use all other version control systems based, let's say file explore. Using explorer which integrates with those types of tools.

 

Joe:Another question that popped into my head is on I know you split up not a lot of different technologies but all the technologies is DIU based or do you also support any type of APRS testing. I know Microsoft services is becoming more and more popular. I'm just curious to know how you handle those types of technology.

 

Christopher:Besides DUI there's a demand on doing web based or web service based test automation as well especially in combination. You can do that within Ranorex studio you have the ability to add libraries for the .Net Framework in order to do web service based testing or deep dive into a database to double check whether a value was set on correctly. For sure you can combine this. Then our customers are using this approach very often.

 

Joe:Is there any trend you see coming up that you think most testers should be aware of that you think is going to be more and more popular in the coming years?

 

Christopher:I think that the biggest trend is driven by agile. I mean everyone is talking about agile but I honestly think that not everyone is sure about the consequences when it comes to changes within the teams. Yes, just sitting down in the team as a testing an agile team doesn't mean that you are communicating on the same level. This is in our opinion apart from the tools, one of the biggest challenges out there that is one thing. Also for sure these type of testers they need to know a lot, they need to understand development approaches, they need to talk to those developers in the same type of language.

 

Also for developers things are changing and then these developers need to accept that testers have a different type of approach and they need to work together a lot closer together. I'm not sure whether this is already this just kind of transition is already completed so far. In terms of technologies, in terms of trends what we see a lot for sure is that a lot of applications are moving away from the desktop to web. Also what we see is that when we talk about mobile testing that there is still unsatisfied situation out there for a lot of testers being new to that topic. Especial in the mobile field, a lot of testers have no experience with testing in general but the strange thing there is that these testers should be a lot better from a technical background.

 

In this situation it really turns out that those tools which are able to provide the easiest access to those way or those applications when it comes to test automation on mobile. Those tools will succeed in future. These are the kind of a trends we see from a team perspective, from on test organization perspective and also from a technology perspective.

 

Joe:Awesome. I want to go off on a rant but what you said about agile so true. I hear a lot of companies that say they're doing agile and what that means is … No, they make everyone be co-located in the large room then they say, “We’re doing agile.” That's all they do. The easiest thing and then they think agile is crazy that companies do that. You're saying the same thing it sounds like.

 

Christopher:We see the same thing because. We are in contact with our customers and it’s true and we're talking to them and then we ask them, “Okay, what kind of develop approach are you using?” They always say, “We do agile.” Then when we ask more, more questions about how testers are talking to developers, where are all these testers located, how about user stories, how about all the stuff you are aware of when you are in the real agile team. It quickly turns out that most of these organizations are not there.

 

Joe:Now the question I have is how would you recommend someone educate their teams how they can start with test automation? One of the biggest questions I get by a lot of people on my blog is, how do I get started with test automation? How do I educate my team to what really is test automation? What is the effort real effort involved to make sure it's not just one person's job? Knowing in agile world that really is everyone's responsibility now I think.

 

Christopher:That's a good question. I mean I when it comes to education from our perspective and apart from the tool vendor, what we see is that people first of all, have to understand which test cases should be automated first. In order to understand this it is essential to have a more basic understanding about testing in general. Everyone knows that there are a lot more test is needed than we have available especially when it comes to automation. You should not just jump on a test case and this will be nice to talk to get automated, all we think about which test cases I can be automated as or can be executed as often as possible because the more often you execute a test the quicker the return on invested is finally.

 

One essential thing here is education. Think about who is doing the automation and always think about the test cases you want to automate. Also from a Ranorex prospective I mean what we try to do and what we do a lot and especially in the couple of last month is we offer lot of free Webinars to train the people on doing automation with Ranorex, to get started not to jump on the on the on the wrong topic. Just to ensure that people are focused on the right topics and also trained them on the big dos and don'ts in test automation. We offer a lot of … Also free available webinars you can download or you can participate live in order to learn how to get started with test automation.

 

Roland:If I may add something here well when I started four and a half years ago I started as a trainer I was doing workshops online but also on site doing trainings. I was also responsible for a technical recommendation that we have. I know from firsthand how hard can be to get started with this topic. What things help to get some skills to requesting or to gather some skills and that's why what we see here is that we would like to provide all the clients out there with the information they need. We don't hide anything.

 

We really provides best practices, we provide our instructions, we provides short videos to explain how to use the tool based. What we also have at the very end if you think that you're done with the basics, you can also do an exam to get Ranorex certificated. To really see, “Okay now has a black and white. This is my certificate so I am able to set up test cases with Ranorex in a very smooth way and in intelligent way.” They can still hold in the future and proves to be graduates and working also for the future.

 

Joe:Awesome. That wasn't me but that sound like a good segue to the very last question. Okay, before we go, is there one piece of actual advice you can give someone to improve their test automation efforts with Ranorex? Let us know the best way to find or contact you more about Ranorex.

 

Roland:Oh it's a very good question. Just start from the very scratch I would say everybody starts with the proof concept to see how you can deal with that. That's a very good starting point and after that I would say sit down make a plan and see what skills you have and find the right job for right person in a team. I don't know, communicate with us in terms of … Visit our website, ask the community in the forum, watch our videos, read our blog posts. Because we had a lot of stories, we've heard a lot of stories what can go wrong and we try to bring back this information so that it doesn't happen in any other team anymore. We [inaudible 00:36:24] and I think you're good with that.

 

Christopher:Another thing I would like to add here especially when it comes to the topic of object identification, everyone knows that UOL test automation is only possible if the tool is capable to automate or to identify certain objects on screen. Also make use of our support team and get in contact with them if you are facing any challenges there. I mean out of the box we have a good support for all of these technologies out there. There is also a good feature included within Ranorex spyware where you can easily share your object identification situation with our support, so that it can easily give you feedback within a couple of hours and tell you, “Hey, listen take care when you deal with this type of object. This one is based on a dynamic ID, I can't provide you with a certain rules that your robust object identification is much more stable in future.” The more you're in contact with us or with our community the higher the chances that are you successful with your test automation project.

 

1 comment
Testing Bits – 5/15/16 – 5/21/16 | Testing Curator Blog - May 22, 2016

[…] Podcasts: EPISODE 102: Test Automation with Ranorex [PODCAST] – Joe Colantonio – https://www.joecolantonio.com/2016/05/19/episode-102-test-automation-ranorex-podcast/ […]

Reply
Click here to add a comment

Leave a comment: