Post
by ngaruko » Fri Jul 29, 2016 4:00 am
I understand that sometimes it makes sense to avoid writing code. But unfortunately, as it stands, there are a number of things we cannot do with Ranorex (like most recorders). These may include passing parameters and receiving feedback from other tools (Powershell in your case, others like SQL command, visual studio etc), doing some logic (looping, iteration, if statements etc). In these cases, I guess it makes sense to use some code to get the most our of your investment. After all, Ranorex has invested in this feature (user code) and other Apis because they know that there is so much one can do with the recorder. And the price we pay for their license include these features! Also consider using other tools for non-UI related tests. Let me paraphrase from Wikipedia: "Ranorex is a GUI test automation framework for testing of desktop, web-based and mobile applications". The accent here is on GUI. For other tests, maybe consider better suited tools and IDEs. Another paraphrase, this time from Abraham Maslow : "I suppose it is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail".
Meantime, if you find ways around these issues and are able to implement them using exclusively the recorder, please share with the community on this forum.
Best of luck!
Last edited by
ngaruko on Mon Aug 22, 2016 4:18 am, edited 1 time in total.