Ranorex VS another automation tool NEED HELP
Posted: Wed Jun 14, 2017 6:09 pm
Hi guys,
my company just received a pre-demo from a company house that is offering us an UI test automation for our testing, now, I've been working with Ranorex for few years, and I'm trying to see what are the main differences between those two softwares.
Meanwhile, my manager asked this other company to give us a comparison between this software and Ranorex, and this was their answer (sorry, can't say the name of the other company).
Here is a collection of how we differentiate ourselves by Ranorex:
- XXXXX is a Module-Based automation tool. Ranorex is a script-based tool
o With the Module-Based approach, the Maintenance can be reduced dramatically.
e.g. By adapting a Module, all related TestCases will been adapted automatically. In a script based tool, you have to adapt every single script.
o XXXXX Testcases are Business-Readable (means: In one view you see what the TestCase is going to execute) – in a script based tool, you need coding skills to read the testcase
- The following bulletpoints are supported by XXXXX, not by Ranorex
o Provide business abstraction for customizations (which any enterprise test automation needs to deal with)
o Non-UI Testing
o Manual Testing
o Exploratory-Testing
- What Customers need to know about Ranorex:
o You must set up a development project to set up a suitable framework for your application.
o Not “Enterprise Ready” across an Enterprise Application Landscape. Only used in “niches”
o No “Continuous Testing” Strategy and no set of functionalities for supporting it.
o No E2E test capabilities on Business process level to realize real “Shift Left”.
o No Virtualization Capabilities to eliminate dependencies of availability in the E2E testing context.
o Feels like a development tool: Before every run a compilation will take place. Ranorex uses an Visual Studio interface. Business users cannot use this tool.
o You need a C# or VB.NET developer for maintaining the test automation framework.
o No test management component, no feedback on the achieved business risk
o No customization interface for custom controls (limited enhancements are possible through custom programming within test scripts).
Could anyone confirm/dismantle what is written in here? I believe, for example, that Ranorex IS module-based AND script-based, you don't need a development project to setup a suitable framework with Ranorex, and so on... but your help would be even better and maybe more precise than mine.
Thank you
my company just received a pre-demo from a company house that is offering us an UI test automation for our testing, now, I've been working with Ranorex for few years, and I'm trying to see what are the main differences between those two softwares.
Meanwhile, my manager asked this other company to give us a comparison between this software and Ranorex, and this was their answer (sorry, can't say the name of the other company).
Here is a collection of how we differentiate ourselves by Ranorex:
- XXXXX is a Module-Based automation tool. Ranorex is a script-based tool
o With the Module-Based approach, the Maintenance can be reduced dramatically.
e.g. By adapting a Module, all related TestCases will been adapted automatically. In a script based tool, you have to adapt every single script.
o XXXXX Testcases are Business-Readable (means: In one view you see what the TestCase is going to execute) – in a script based tool, you need coding skills to read the testcase
- The following bulletpoints are supported by XXXXX, not by Ranorex
o Provide business abstraction for customizations (which any enterprise test automation needs to deal with)
o Non-UI Testing
o Manual Testing
o Exploratory-Testing
- What Customers need to know about Ranorex:
o You must set up a development project to set up a suitable framework for your application.
o Not “Enterprise Ready” across an Enterprise Application Landscape. Only used in “niches”
o No “Continuous Testing” Strategy and no set of functionalities for supporting it.
o No E2E test capabilities on Business process level to realize real “Shift Left”.
o No Virtualization Capabilities to eliminate dependencies of availability in the E2E testing context.
o Feels like a development tool: Before every run a compilation will take place. Ranorex uses an Visual Studio interface. Business users cannot use this tool.
o You need a C# or VB.NET developer for maintaining the test automation framework.
o No test management component, no feedback on the achieved business risk
o No customization interface for custom controls (limited enhancements are possible through custom programming within test scripts).
Could anyone confirm/dismantle what is written in here? I believe, for example, that Ranorex IS module-based AND script-based, you don't need a development project to setup a suitable framework with Ranorex, and so on... but your help would be even better and maybe more precise than mine.
Thank you