Welcome!

Microservices Expo Authors: Pat Romanski, Elizabeth White, Liz McMillan, Yeshim Deniz, Carmen Gonzalez

Related Topics: Java IoT, Industrial IoT, Microservices Expo, Microsoft Cloud, Machine Learning , @CloudExpo

Java IoT: Product Review

Product Review: qTest by QASymphony

A comprehensive testing tool

QASymphony is the company behind qTest, a new test management tool that's aiming to empower test teams. As software development has increasingly moved towards Agile methodology, with its focus on fast delivery, thorough documentation has fallen by the wayside and test cycles have shortened. Test teams have less time to identify and document defects, but expectations for bug-free software remain high. The flexibility to adopt feedback and accelerated build cycles offer real benefits for software development, but they require careful thinking from QA departments.

These are the challenges that qTest is trying to address by equipping testers with a fast, intuitive tool capable of handling complex projects. It's designed to be easy-to-use, it's fully customizable, it can plug into existing bug tracking software, and it creates a chain of transparency that lays bare the entire life cycle of each defect. It should be a tool that's appealing to teams trying to save time by implementing agile testing. Like so many new releases nowadays, it is a SaaS solution, based in the cloud and it's offered at $20 per month per user. The 30-day free trial gives you five licenses, so you can test it out for yourself. How does it measure up?

Activation
Getting started with the qTest software is pretty simple. Head to the QASymphony website and you too can test the five-minute setup claim. When you click "Try qTest Free" you'll be asked to fill in your name, provide an email address, company name, create a site address (which is your cloud-based home on QASymphony's server), and choose a password. You'll get a confirmation email with a link to verify your account, and then you sign in and voila! You should now be looking at your administration panel.

There's no software to install and, since it's cloud-based, you can access your projects from anywhere. So far, so good.

Getting Started
New tools always take a bit of getting used to. Thankfully, upon entering qTest, you'll be greeted by a pop-up window entitled "Five Minute Quick Guide." It consists of bite-sized chunks of info, complete with screenshots, on how to create a new project, invite other users, and dictate roles and permissions. The help guides are context sensitive, because when you enter an actual project you'll find new guides that cover creating requirements, importing test cases, and so on.

Initial impressions are that the interface is streamlined. Everything is clearly labeled, and the main bar at the top offers you navigation options. There's an inevitable, slight lag as each new section loads up. You'll also notice a bit of lag as well when you create a new project or start to add requirements, but on the whole it's fairly snappy and accessible.

Features
What does it actually do? Once you create a project and add your start and end date, and any other admins, you can start to populate it. You'll find the following options in your navigation bar at the top - Test Plan, Requirements, Test Design, Test Execution, Defects, and Reports. These options are followed by a tools menu that allows you to configure user permissions, custom fields, external systems, notifications, and environments. The final option is the help guides, where you can also submit bugs or feature requests for the qTest tool.

As you enter each section you'll see the panel on the left-hand side get updated. This is where you can create a tree of project modules and their attendant requirements, test cases, and defects. If you've already been using a defect-tracking solution, like Jira or Bugzilla, or you have test cases written up in Excel documents, you can start by importing data. That option works both ways - you can also export XLS files. To link up an external system go to Defect Management in the tools menu and all new defects you enter in qTest will be automatically exported and vice versa.

If you're starting from scratch then you'll enter your Test Plan, which isn't intended as a project management tool, but rather as a way for QA teams to track the build release schedule. The Requirements, or user stories, come next and you can actually create Test Cases directly from the same screen, which is a real time-saver. Once again there will probably be some overlap with your project management system, but having a requirements module in here is a good way to uncover gaps in the documentation, provide extra detail, and provide traceability because the full history is recorded.

Test case management is provided in the Test Case module. It seems that qTest understands that testers like to work with Excel, so the test case editor looks and works a lot like Excel. It's quite easy to create, edit test steps and move them around.

You'll then move on to Test Execution where you can create and structure your Test Cycle, Test Suite, and Test Runs. When you've planned out the tree you can move on and actually execute a Test Suite. When you click Run you'll get a Testpad pop-up where you can enter expected and actual results, attach files, mark each step as a pass or fail, tweak the steps as required, and, of course, enter any defects you encounter. It's possible to use QASymphony's screen capture qTrace tool alongside the Testpad to record steps and screenshots that can be added to a defect report.

qTest has a full Defect module so you don't have to get another tool to manage defects. But if you are wedded to a defect tracking tool, qTest gives you the option to turn off the internal tool and use an external tracker. It seems that qTest is able to integrate with Jira, Bugzilla, Fogbugz, as well as Rally and VersionOne ALMs.

It's fairly straightforward to work through and if you run into any problems the help guide is a click away. You'll also find that the Notification icon in the top right of your interface provides useful, real-time updates about what's happening on your project. You can click directly on these to go to the relevant defect or test case. The full chain of actions on every element is recorded for full transparency.

At the far top right there's a powerful syntax search tool, so as the project grows you should still be able to jump directly to whatever you are looking for quickly. You'll also find the Reports section increasingly useful over time as it offers analysis, which can be filtered by fields, values, or dates. You can also create your own customized reports based on your choice of metrics. The nice thing about the reports screen is that you get a single place to see the project progress at-a-glance and filter by date or field. You can also drill down further and bring up defect details in a list on the same screen.

Usability
You really can get up and running with qTest within minutes. The interface is clean and uncluttered, which makes it easy to come to grips with. The full history on each record makes it clear who did what. The real-time updates work well for collaboration.

There's obviously a fair bit of work to do to create your project and it's worth planning carefully to ensure that you have things set up correctly before you invite the rest of the test team onboard. When your Test Plan is ready, the actual implementation couldn't be easier. Any field that can be automatically filled is dealt with by qTest, so testers can really focus on identifying and describing defects. Related records are linked and the ability to create test cases directly from requirements makes perfect sense.

Tracking your test results via the Testpad pop-up without having to leave the application you are testing is very convenient. Just like the ability to clone defects, it's a time-saving feature that enables testers to work faster.

Room for Improvement
No product is ever perfect and qTest is still being developed, so there are inevitably a few improvements that could be made. And while it's nice to see a rich text editor option for the Requirements, because it is quite rare in test management tools, sadly it isn't extended to comment fields or defect descriptions. qTest runs on a browser, so it actually is supported on a Mac and Linux.

There is an option via the Help icon in the navigation bar to submit tickets for defects in qTest to the QASymphony team and to request new features. Responses are fast, the development team will confirm whether they will be implementing your suggestions and give you a timeline. They are currently updating qTest once or twice a month, so bug fixes are fast and there's a good chance they'll accommodate feature requests.

Verdict
This is a really comprehensive testing tool and it works hard to fit in with the ethos of Agile development. The automated fields, linked records, and complete history are invaluable for test teams. Not only is qTest helping to increase speed and efficiency, but also to provide transparency. Compared to existing solutions, at first glance, qTest ticks all the same boxes, but there are a lot of little touches that you won't find elsewhere. The end result is a smooth workflow and a dynamic, robust system that's extremely accessible.

This is a competitively priced, scalable solution that any company could adopt instantly, without any hardware or software setup. Clearly QASymphony is focused on empowering testers. Compared to traditional test management systems, which are complex, expensive, and suffer from a steep learning curve, qTest is a breath of fresh air.

More Stories By Kaushal Amin

Kaushal Amin is Chief Technology Officer for KMS Technology, a software development firm with 300 employees and offices in Atlanta and Ho Chi Minh City, Vietnam. You may reach him at [email protected]

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
Building custom add-ons does not need to be limited to the ideas you see on a marketplace. In his session at 20th Cloud Expo, Sukhbir Dhillon, CEO and founder of Addteq, will go over some adventures they faced in developing integrations using Atlassian SDK and other technologies/platforms and how it has enabled development teams to experiment with newer paradigms like Serverless and newer features of Atlassian SDKs. In this presentation, you will be taken on a journey of Add-On and Integration ...
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership abi...
The essence of cloud computing is that all consumable IT resources are delivered as services. In his session at 15th Cloud Expo, Yung Chou, Technology Evangelist at Microsoft, demonstrated the concepts and implementations of two important cloud computing deliveries: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). He discussed from business and technical viewpoints what exactly they are, why we care, how they are different and in what ways, and the strategies for IT to transi...
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm.
As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and micro services. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your contain...
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningf...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In his Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore t...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, explored HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
With major technology companies and startups seriously embracing Cloud strategies, now is the perfect time to attend @CloudExpo | @ThingsExpo, June 6-8, 2017, at the Javits Center in New York City, NY and October 31 - November 2, 2017, Santa Clara Convention Center, CA. Learn what is going on, contribute to the discussions, and ensure that your enterprise is on the right path to Digital Transformation.
Everyone wants to use containers, but monitoring containers is hard. New ephemeral architecture introduces new challenges in how monitoring tools need to monitor and visualize containers, so your team can make sense of everything. In his session at @DevOpsSummit, David Gildeh, co-founder and CEO of Outlyer, will go through the challenges and show there is light at the end of the tunnel if you use the right tools and understand what you need to be monitoring to successfully use containers in your...
What if you could build a web application that could support true web-scale traffic without having to ever provision or manage a single server? Sounds magical, and it is! In his session at 20th Cloud Expo, Chris Munns, Senior Developer Advocate for Serverless Applications at Amazon Web Services, will show how to build a serverless website that scales automatically using services like AWS Lambda, Amazon API Gateway, and Amazon S3. We will review several frameworks that can help you build serverle...
The IT industry is undergoing a significant evolution to keep up with cloud application demand. We see this happening as a mindset shift, from traditional IT teams to more well-rounded, cloud-focused job roles. The IT industry has become so cloud-minded that Gartner predicts that by 2020, this cloud shift will impact more than $1 trillion of global IT spending. This shift, however, has left some IT professionals feeling a little anxious about what lies ahead. The good news is that cloud computin...
SYS-CON Events announced today that HTBase will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. HTBase (Gartner 2016 Cool Vendor) delivers a Composable IT infrastructure solution architected for agility and increased efficiency. It turns compute, storage, and fabric into fluid pools of resources that are easily composed and re-composed to meet each application’s needs. With HTBase, companies can quickly prov...
An overall theme of Cloud computing and the specific practices within it is fundamentally one of automation. The core value of technology is to continually automate low level procedures to free up people to work on more value add activities, ultimately leading to the utopian goal of full Autonomic Computing. For example a great way to define your plan for DevOps tool chain adoption is through this lens. In this TechTarget article they outline a simple maturity model for planning this.
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations might...
The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Software development is a moving target. You have to keep your eye on trends in the tech space that haven’t even happened yet just to stay current. Consider what’s happened with augmented reality (AR) in this year alone. If you said you were working on an AR app in 2015, you might have gotten a lot of blank stares or jokes about Google Glass. Then Pokémon GO happened. Like AR, the trends listed below have been building steam for some time, but they’ll be taking off in surprising new directions b...