Comprehensive software reviews to make better IT decisions
Select Your Open-Source QA Tools With Eyes Wide Open
It is difficult to not talk about open source in a QA tooling discussion. Over the past decade, open-source tools flooded the market and changed the way organizations managed and executed QA activities. Several of these tools made significant strides to become staples in the industry, such as (Sauce Labs):
- Selenium: A test automation tool that automates actions in the browser
- Appium: The mobile counterpart to Selenium used for automated testing on both iOS and Android
- JMeter: A performance testing tool written in Java
- JUnit: A unit testing tool for Java applications
- Robotium: Records UI tests for Android
- Selendroid: Selenium-based automated testing for Android
The decisions on which open-source tools and how you leverage them are dependent on the desired tool feature, implementation, and management capabilities, such as:
- A tool’s specialty in a specific type of test on a specific platform using a desired approach. Open-source tools tend to focus on a specific testing problem, whether that be test management or execution.
- The discussions, collaborations, and activeness of open-source community to support your tool. The help and advice in these communities may not meet your immediate support needs.
- Diverse support for open-source tools through extensive partners and sponsors. Selenium, for example, is widely supported through out-of-the-box plugins provided by partners. Some vendors, such as Sauce Labs, incorporate open-source tools within their proprietary toolsets. However, support is often provided to only recent versions of the open-source tool.
- Customizable and extensible across multiple proprietary product delivery tools, such as application lifecycle management, test management, and delivery work management tools. However, these vendors may have invested interest in specific open-source communities and tools, which may lead to biased treatment. Ultimately, you may be left on the hook for support if the vendor decides to shift gears.
Despite their prevalence in the industry, open-source QA tools may not be as valuable or useful as advertised. Unique organizational and team implementation, management, and support challenges may restrict the full realization of the tool’s benefits or introduce unintended financial and vendor risks. Get a firm grasp on these key items as you architect and select your QA tools to justify their value:
- Testing and QA tooling capability gaps
- Product delivery tooling landscape and integration needs
- Desired vendors that incorporate open-source tools within their own toolset
- Open-source management practices
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.