Comprehensive software reviews to make better IT decisions
SmartBear Releases Zephyr 6.6 and Acquires TM4J
SmartBear’s Zephyr gives teams the capabilities to manage testing and QA activities within the Jira ecosystem or as a standalone tool. The 2018 acquisition of Zephyr extended Zephyr’s test design and execution capabilities through the experience of SmartBear’s staff and its integration with SmartBear’s portfolio, such as SwaggerHub, HipTest, CrossBrowserTestin, and SoapUI Pro. This vendor also wanted to extend its extensive testing management capabilities beyond the users of its Jira edition of Zephyr. Enter the standalone Zephyr Enterprise Edition.
The recent Zephyr 6.6 release demonstrates SmartBear’s commitment to extend its market reach and minimize the dependence on the Atlassian customer base. Some notable updates include:
- Enterprise Admin & Scaling. For larger customers scaling their Zephyr deployments, significant improvements were made to the SSO and LDAP support. It added the ability to provide read-only access to test assets, created a new API token management page and updated the REST APIs, zBots, and plugins to accept tokens instead of user credentials, and continued improvements for audit logging.
- Automation Improvements. Simplified installation and setup for zBots by providing a single downloadable version that is also auto-configured for the user; and rearchitected the automation parsers, enabling customizations for homegrown and custom frameworks as well as consistent behavior across of tools that work with Zephyr (Vortex, Folder Watcher, zBots, and CI plugins).
- Usability Improvements. Improved the Jira defect filing page for better performance and support for pre-populated fields, and underwent an overhaul of the Zephyr look and feel.
In addition to the Zephyr 6.6 major and subsequent minor releases, SmartBear announced its acquisition of Test Management for Jira (TM4J) from Adaptavist, which does not come with much surprise given TM4J’s support of Cucumber and SmartBear’s acquisition of Cucumber in June 2019. Similarly to Zephyr’s Jira edition, TM4J extends the test management capabilities of Jira with an out-of-the-box plugin, but its direct support of behavioral-driven development (BDD) with Cucumber, or a chosen Gherkin compatible tool, makes TM4J a key differentiator. SmartBear has not announced any significant changes to the TM4J and Zephyr products but is looking to dedicate additional investments to enhance these tools’ strengths and compatibilities.
The recent release of SmartBear’s Zephyr Enterprise Edition shows this vendor’s dedication to compete against the bigger players in the space, such as IBM, Micro Focus, and Microsoft. Its recent TM4j acquisition is just one of several strategic acquisitions of testing solutions in the past few years, a common pattern we see in the application lifecycle management (ALM) marketplace. We have yet to see how SmartBear will position TM4J and its various product offering as key differentiators against its competitors. Only time will tell.
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.