Comprehensive software reviews to make better IT decisions
Ranorex Studio Release Focuses on Testing Productivity
Ranorex Studio provides quality assurance (QA) teams with a framework to implement, manage, and orchestrate automated testing. A full version release with enhanced and new features is made at the beginning of each year, and minor releases and updates are completed throughout the year to address issues and bugs. Third-party integrations are limited compared to other vendors (such as Micro Focus and Microsoft), but its list of integration partners is slowly expanding with every release, including TestRails (release 8.1.0) and JIRA (release 9.1.0).
Release 9.1 earlier this year enhances the testing experience with improved integrations, monitoring features, and scripting capabilities. Notable new features include:
- Automatically identify, analyze, manage, and track user interface (UI) elements of an application in order to define and execute UI tests. This feature is performed with the Ranorex Spy and RanoreXPath tools.
- Integrate Ranorex Studio with Jira and create issues for test cases manually or automatically.
- Monitor failed or passed test cases in real-time, including the number of test containers already executed, their status, and time elapsed.
Release 9.1 builds upon the significant improvements of release 9.0 made in early 2019, such as:
- Visualization of the time to execute test operations for continuous improvement
- JxBrowser support
- Shadow DOM support
- Dynamic ID recognition for web elements to improve the robustness of test cases
- Ability to record videos of all test cases or just failed test cases
- Support for using target frameworks up to .NET 4.7.2, compiling C# 7.0, and building with MSBuild 15
Ranorex may not be the biggest player in the space, but its dedicated focus on the testing space makes it a serious option for managing test automation. This vendor is transparent on the growth and evolution of its Ranorex Studio product and strives to deliver features that users want. It is yet to be seen where and how Ranorex Studio will evolve in the future.
Want to Know More?
Traditional accounting practices are tailor made for waterfall project management. Organizations that have transitioned to the use of standing product teams using Agile and DevOps need to transform their accounting practices as well or they will leave valuable capital expenditure dollars on the table.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
Do you feel like your Agile teams are treading water – going through the motions but never going anywhere? It’s a risk, and practices such as daily standups, retrospectives, and demonstrations need to be used wisely or you risk losing discipline to meeting fatigue.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.
Aha! introduces scenario planning to give product owners the ability to create and compare multiple release approaches based on team capacity and backlog priority.