Mobile Apps Can Improve Customer Service… What About QA?

A new article from Infostretch explains how mobile apps can help improve customer service.  It is a great article that explains the need to think mobile to improve customer service.

There is no doubt companies need to plan for mobile, but are they ready to test mobile?  Mobile brings many complex user stories that need to be tested now that your app might be interrupted by a phone call, low battery, or other interrupt, but every device is different.  What works on one device may not work on another.  Even if you have worked out all the details the question remains: can your testing tool support you?

QMetry 6 provides an unprecedented level of support for mobile testing teams.  In addition to being able to create complex test scenarios from a central repository QA teams can use QMetry’s advanced platform management tool to validate functionality across multiple mobile devices.  Read more about QMetry’s Advanced Platform Support.

And read about Better Customer Service through Mobile Apps on the InfoStretch blog.

Improved Integration with JIRA

QMetry 6 continues to improve its integration with JIRA as well as overall performance.  With the latest release API Enhancements have been made to further help automation teams get the most out of the QMetry integration with their automation tools.

For more information on this release read the QMetry 6.6 Release Note.  If you are already familiar with QMetry 5 read our   What’s New in QMetry 6 page on the support site to better understand the major difference between the version 5 and 6.

Reporting on Testing Has Never Been Easier

With the most recent release of  QMetry reports have advanced again.  QMetry 6 continues to add new reports, many of them unique in the industry to help QA teams establish test coverage.

QMetry Test Manager comes with many unique built in reports designed to help organizations view both test progress and test coverage. Our 100+ reports can also be customized and even copied to create new reports that better fit your organizations needs. And our reporting engine even works with user created custom fields.

For more information on this release read the QMetry 6.5 Release Note.  If you are already familiar with QMetry 5 read our   What’s New in QMetry 6 page on the support site to better understand the major difference between the version 5 and 6.

Migration From QMetry 5 to 6 has begun!

Migration of existing QMetry 5.x customers has begun with the recent release of QMetry 6.4.  The installed base is now starting to enjoy the performance boost and advanced features of QMetry 6 as they migrate the industry’s premier test management tool.

For more information on this release read the QMetry 6.4 Release Note.  If you are already familiar with QMetry 5 read our   What’s New in QMetry 6 page on the support site to better understand the major difference between the version 5 and 6.

What Challenges Will You Face When Testing Wearable Devices?

Every application testing situation presents new challenges. Do you have the experience and knowledge to adjust accordingly?

InfoStretch recently tested and quality assured a digital health feedback system for Proteus Digital Health. The Proteus service offering integrates the intake of medicine with ingestible sensors, wearable devices and data analytics to make healthcare more accessible, manageable and affordable.

Read the Full Article

QMetry 6 Continues to Advance

New Custom Statuses and Much more are packed into the latest release of QMetry 6 which continues to break new ground in test management.

In addition to new features QMetry 6.3 provides a major performance improvement designed to handle large scale enterprises.  Performance of QMetry 6 already outpaced QMetry 5 and other competitors; however, with changes in version 6.3 provide the performance needed for thousands of users, hundreds of thousands of test cases, and all the complexity of organizing those assets into various folders and linking assets between modules.

For more information on this release read the QMetry 6.3 Release Note.  If you are already familiar with QMetry 5 read our   What’s New in QMetry 6 page on the support site to better understand the major difference between the version 5 and 6.

Official Release of QMetry 6.2

QMetry 6 is official released to new customers.  The release comes in time to support the largest customer in QMetry’s history, Dell.  For more information on this release read the QMetry 6.2 Release Note.

A new  What’s New in QMetry 6 page has been added to the support site to better understand the major difference between the version 5 and 6.

Why Use a Test Management Tool

Many companies can get by in the early stages without a test management tool.  Often testing is done ad hoc against features that are outlined in a requirement management tool like Rally and Version One, or a bug tracking tool like JIRA and Bugzilla.   In the early stages with a good development team using best practices of short development practices, good code review, and proper unit testing bugs won’t often slip through.  The code is small enough that the development team are on top of all the changes.  In the early stages compatibility is often not a factor of concern- whether the product works in all environments is not important since there are not customers to support, and/or only a few target customers that the team needs to support.

As the customer base grows, and/or the market expands ad hoc testing starts to show limitations as it misses coverage of more and more of the products functionality.  As the lines of code increases software developers lose track of the full scope of the code, and it becomes harder to anticipate the effects of a change.  As the hardware gets more complex, or the installed base grows, hardware teams must consider support of products in the field as well as the new hardware needed to keep up with market changes and capture new accounts.

Why not Excel?

Excel is a great first step; however, Excel does not allow organizations to centrally control test cases, making it hard to find and reuse test case assets to cover different user stories.  This leads to multiple versions of test cases and a lot of redundancy.  With Excel information is not available to everyone,  you have to send the excel sheets to each other, or store them in some central location that will likely  have its own limitations.  Trying to find the right set of test cases can turn into a problem as the project grows.  Reporting is perhaps the biggest challenge.  Teams using excel will often be using many different excel sheets to record results.  The results will not be visible until the are collated, and that takes time and usually requires the manager to do the bulk of the work.    One manager I spoke to testing mobile phone apps for a major carrier had to spend 1 day every two weeks just to gather the reports from testers in the field and put them in the proper format to then report to upper management on the progress.  Luckily the weekly report for the internal team only took an hour or two to generate.

These problems all become worse with distributed teams that not only need to share resources, but need to be assigned tasks as well.

At the highest level a test management tool will help any team with just the simple task of centralizing the test repository,  and automatically generating and updating reports.  Most come with at least some task / assignment management helping teams distribute the workload to become more efficient with the team’s resources.

Test Management tools like QMetry add true enterprise level version control, integration with bug tracking so developers can get high quality bug reports and QA can save time in re-entering steps to reproduce.  The rich reporting in advanced tools like QMetry also provide far more information to both the QA team and management to understand that status and progress of testing in real time.

New Tools for Agile Development

With today’s fast pace of development it is important to move and adapt to change.  With change comes risk, and that is what quality assurance is there to mitigate.  Some of the old traditional test management tools were bulky and required strict adherence to a formal procedure.  This was fine for long development cycles with ample time to test, but in today’s world most teams struggle for even extra few days of testing.  Many of the old tools emphasized long reports showing a full review of all testing to prove that testing was done.  Testing should never devolve into a CYA activity, instead a test management tool should empower the QA team to work in tandem with development and provide immediate feedback and reporting so quality and performance problems are identified in real time and can be acted upon in short order.

While QMetry has all the features to support a traditional development cycle it has been enhanced to provide function well with more fast paced teams that need to run with development and improve collaboration with the focus on improving quality and efficiency.  Teams can focus on testing not managing test assets, assigning tasks, or creating reports.

QMetry Beta Program Advances Toward Release of QMetry 6

QMetry 6 was updated to the beta testers on July 9th allowing the users to test out the improvements to QMetry’s already industry leading platform testing functionality.  A long list of additional user interface enhancements including full support for localization is currently being tested by the beta testers.  For more read the QMetry 6.1 Release Note.

QMetry 6.0 in Limited Release

QMetry 6 was delivered to a small group of  beta testers to provide feedback on the new user interface and functions in development.  The initial feedback is excellent with beta testers enjoying the faster performance and ability to multi-task.  For more read the QMetry 6.0 Release Note.

 

Try QMetry Total Test Management for Free

30 Day Free trial. Test Management made simple.