QMetry 6.8 is released

InfoStretch is proud to announce the release of version 6.8 for OnPrem customers of QMetry Test Manager.  QTM 6.8 comes with fantastic new features, a lot of enhancements, and some bug fixes for all QMetry users.  Great improvements to usability with enhancements to how windows open, and the addition of Saved Views to the Execution Screen.

The export feature has also been upgraded to better handle large very exports and give some administrative oversight.

Also added is improved audit logs to help QA Managers and IT admins to better monitor and review changes in the system.  Read More about QMetry 6.8.

If you are a QMetry 5 user and you want to understand the major difference between the two version please read our What’s New in QMetry 6 page.

 

How QMetry with JIRA Compares to Other Enterprise Tools

Enterprise QA tools provide a rich feature set for large organizations with concerns about quality.  The main characteristics for an enterprise QA tool is the ability to scale both in supporting the number of users, and the number of test cases. There is also a need to be able to support multiple products and/or variations of a single product.  Test assets need to be reused often across multiple groups so version control and test execution history is often a big concern.

There are many enterprise QA tools available that have robust feature sets and most offer some sort of JIRA integration.  Some claim they have the best JIRA integration; however, we just ask for you to compare the tools side by side.  There are many things to consider, but in the end the reason why you would use QMetry versus a customized JIRA solution and the reason why you would use QMetry versus a JIRA Plugin will also determine why to use QMetry versus another enterprise tool. JIRA is a great defect tracker, and QMetry provides the best of class test case manager with a superior integration with JIRA.

There are hundreds of features that enterprise class test management systems offer.  Here is the list of features that QMetry excels in over the competition:

  • Ability to setup an automatically import issues as requirements based on a simple filter or complex JQL query.
  • Real-time Test Case information in JIRA
  • Platform Support – Ability to Execute Test Suite against various platforms and generate reports for executions across different Releases and Cycles.
  • Advanced Search with ability to perform Boolean Searches.
  • Support for Continuous Integration.
  • Ability to organize test assets into folders and sub-folders and view the test status at the folder level.
  • Ability to edit test cases during an execution.
  • Ability to choose particular version of the test case to be executed during execution.
  • Support of Rich Text Format in test case steps.

To find out how QMetry can help you improve quality and shorten your development cycle, click here.

Why use QMetry versus a customized JIRA solution?

JIRA is a great tool for managing issues and for simple test requirements; however, using JIRA for test case management can prove difficult for complex testing requirements.  While JIRA relatively flat database structure offers a clear and easy to use interface it doesn’t handle the complexity needed by QA groups that need to create test cases for multiple different test scenarios, or validate functionality and UI against multiple different test environments.  Also a development issue once created has a linear progression.  It is opened, in progress, and then closed (hopefully).  The issue might get reopened, but not on a regular basis.  A test case on the other hand is most often used repeatedly.  First to validate a new feature, and later to validate the existing feature still works.  It may also be updated as functionality is added or enhanced while on the development side an enhancement is considered a new issue.

While at first JIRA test case management may seem like a good solution it will often bog down as the number of test cases increases.  Managing a growing set of active test cases is not what JIRA was built for.  QMetry’s user interface was designed to help QA teams organize and manage large number of test assets for reuse throughout the product life cycle.

QA challenges that lead QA teams choose QMetry over JIRA alone:

  • The product that needs to be tested against multiple different hardware and software configurations
  • The features need to be tested using different test scenarios
  • QA needs to plan out their testing and provide total test time estimates for regression testing and status updates
  • QA teams want full version control and the ability to verify what specific version of a test case was tested
  • Management wants to be able to see what the test coverage is
  • Management needs an overall better set of reports
  • Developers want bugs to be reported with full environmental details.
  • Organization wants to integrate manual and automated testing

With strict policies and procedures you can try to use JIRA (or a JIRA plugin) for some of the above scenarios; however, there will be limitations. And these limitations and human errors will leave gaps in the test coverage and reporting.  Organizations who rely on manual test case creation from JIRA may often find that test cases are not created for many JIRA issues leaving incomplete test coverage.  A simple test case may validate a features as working in one circumstance, but not for other scenarios that will be found in the field (Read more about dealing with complex test scenarios).

Capturing environmental information when filing bugs from JIRA based test cases is also a problem. Creating the bug is easy, but making sure that all the test steps and environmental factors are recorded is largely a manual task and subject to human error.  Poorly recorded bugs can lead to a lot of wasted time and frustration with that circular argument we have all heard “But it works on my machine!”.  (Read more about Logging Defects).

Key Advantages

  • Only import issues as test requirements based on specific search criteria (e.g. Status = Fixed)
  • Automatically link test cases associated to requirements in QMetry to the original JIRA issue
  • Real-time test case information from JIRA
  • Timely Coverage information
  • Ability to group multiple Test cases into a test scenario, what we call a Test Suite.
  • Ability to quickly test and compare test suites against various platforms.
  • Version Test Cases and ability to track changes across different versions.
  • Support for different Automation Frameworks to integrate automated test results with manual test results for one clear
  • Robust reporting Capabilities of QMetry
    • Over 100 reports designed by QA teams for reporting on performance and quality to users and management
    • Ability to create custom reports, with access to the underlying Database Schema of QMetry
    • Professional Services available for creating Custom Reports
    • Unique Coverage Status and build reports that provide powerful insights on testing

The best reason to choose integrating QMetry with JIRA is for the high efficiency and improved workflow for planning and building test coverage, and then actually running test executions. Instead of creating a test case one bug at a time, QMetry allows users to import Test Cases into QMetry from JIRA using a simple search criteria (e.g. Status = Fixed).

By importing issues from QMetry, rather than randomly creating them in JIRA, QA is able to plan out their testing cycles.  It is recommended to import JIRA issues as Requirements. This allows multiple test cases to be link to or create from the JIRA issue. This workflow ensures that both functional, UI, and regression testing is covered. Using requirements also provides a much more comprehensive view of test coverage.

And although testing is done outside of JIRA QMetry use of JIRA’s API allows them to have a full and robust view of the testing status without leaving JIRA. This allows developers to see the linked test requirements and/or test case(s), with their status across the various test suites and platforms they are linked to.

In the end quality assurance is about catching human errors and you want a tool that improves quality and efficiency so that you can keep to your development schedule with a high confidence of release a quality product.

If all you need is a one to one mapping of issue to test case using JIRA (or a JIRA plugin) might work for you.  If you have more complex needs then you should investigate how QMetry can provide you 100% test coverage.  To find out how QMetry can help you improve quality and shorten your development cycle, click here.

Why use QMetry versus a JIRA Plugin?

There are many JIRA test case management plugins that look like great options.  For simple testing needs a JIRA plugin can be very efficient.  Everything is kept in one tool which should mean a low learning curve.  Since the test cases reside in JIRA and the reports are in JIRA everyone has access to the same information.  There is no arguing that this is a very good solution for many companies; however, the JIRA test management plugins on the market do have some limitations versus an enterprise test management tool like QMetry Test Manager (QTM).

Although QMetry Test Manager is a separate application the good news is that QTM still provides a lot of data directly into JIRA so that developers never have to leave JIRA to get the information they need.  Using JIRA’s API all testing from QMetry can be seen within JIRA in context.  And since the API based solution is available for both SaaS and Cloud customers all JIRA customers can use QMetry’s integration without worrying about a plugin.

There are many QA challenges that lead QA teams choose QMetry over a JIRA Plugin.  Below is a list of a few of the key issues:

  • The product(s)need to be tested against multiple different hardware and/or software configurations
  • Management wants to be able to see a more completed picture of the test coverage is.
  • Management needs an overall better set of reports on status of testing and quality
  • There is a need to report on testing between different platforms
  • There is a need to report on testing between different builds
  • QA teams want full version control and the ability to verify what specific version of a test case was tested
  • Developers want bugs to be reported with full environmental details.
  • Organization want to integrate manual and automated testing

Capturing environmental information when filing bugs from JIRA based test cases is also a problem. Creating the bug is easy, but making sure that all the test steps and environmental factors are recorded is largely a manual task and subject to human error.  Poorly recorded bugs can lead to a lot of wasted time and frustration with that circular argument we have all heard “But it works on my machine!”.

Key Advantages

  • Only import issues as test requirements based on specific search criteria (e.g. Status = Fixed)
  • Automatically link test cases associated to requirements in QMetry to the original JIRA issue
  • Timely Coverage information
  • Ability to group multiple Test cases into a test scenario, what we call a Test Suite.
  • Ability to quickly test and compare test suites against various platforms.
  • Version Test Cases and ability to track changes across different versions.
  • Support for different Automation Frameworks to integrate automated test results with manual test results for one clear
  • Robust reporting Capabilities of QMetry
    • Over 100 reports designed by QA teams for reporting on performance and quality to users and management
    • Ability to create custom reports, with access to the underlying Database Schema of QMetry
    • Professional Services available for creating Custom Reports
    • Unique Coverage Status and build reports that provide powerful insights on testing

The best reason to choose integrating QMetry with JIRA is for the high efficiency and improved workflow for planning and building test coverage, and then running test executions. Instead of creating a test case one bug at a time, QMetry allows users to import Test Cases into QMetry from JIRA using a simple search criteria (e.g. Status = Fixed).  Plugins rely on the manual creation of test cases from issues and there is no high level view of the coverage status.  In essence, a plugin is not using JIRA to manage testing.

By importing issues from QMetry, rather than randomly creating them using a plugin, QA is able to plan out their testing cycles.  It is recommended to import JIRA issues as Requirements. This allows multiple test cases to be link to or create from the JIRA issue. This workflow ensures that both functional, UI, and regression testing is covered. Using requirements also provides a much more comprehensive view of test coverage.

And although testing is done outside of JIRA QMetry use of JIRA’s API allows them to have a full and robust view of the testing status without leaving JIRA. This allows developers to see the linked test requirements and/or test case(s), with their status across the various test suites and platforms they are linked to. This level of detail is not available from the plugins.

In the end quality assurance is about catching human errors and you want a tool that improves quality and efficiency so that you can keep to your development schedule with a high confidence of release a quality product.

To find out how QMetry can help you improve quality and shorten your development cycle, click here.

Cut Your Regression Cycle by 75 Percent

The biggest challenge for QA groups is how to complete the regression cycle.  The problem is often worse for Agile teams- in fact some QA teams struggle to get time to complete any regression testing.  QMetry helps to organize your test cases and improve efficiency, but to truly keep up with regression as your team grows you need to build up a good automated regression suite, and Continuous Integration (CI).  Fortunately QMetry integrates well CI.

Recently the services arm of InfoStretch has helped some of our customers cut down regression cycles by 75% or more. Here’s the core of how they did it.

Introduce Continuous Integration tools

Regression Testing

Regression runs can be done overnight or over the weekend. Compare this to manually entering and monitoring scripts during working hours and there’s no contest on regression speed and efficiency. But you will need Continuous Integration (CI) tools like Jenkins – CI to be able to able to manage automated regression runs.

There are a lot of other very strong reasons for introducing CI tools. As a starting point, there’s early defect detection, reduced overheads, better project visibility and reduced assumptions.

Automate more

There is always a little controversy in deciding the right amount of testing to automate. But common sense should prevail. If it is more time-efficient to create automation scripts once and re-use them, then that is what should be done.

But don’t stop when you have created test automation scripts. There can be many other elements outside of the core testing that can be automated. For example, think about automating the loading of the software to be tested, configuring servers and posting results.

For instance each QMetry build is automated to be created, installed, and then tested using a simple script which any user can kick off.  The tests are run through QMetry Automation Studio (QAS) which provides some basic pass / fail reports. QAS also sends the individual test results to QMetry where they can be further analyzed.  If the build is accepted the manual testers will just continue adding their test results tagging each new manual test with the same build.

This process not only does this allow us to move quickly, but allows us to compare our manual and automated test results based on builds.

Connect all the pieces

Any setup where the individual components do not talk to each other means your efficiency will be leaking away. Having one integrated view of all testing provides a single comprehensive view of the test data.  QMetry’s advanced reporting engine allows management to see the 1000 ft. view of the testing or drill in to get a granular view of the testing.

So, even if it’s tougher at the beginning, integrate the core tools in your testing portfolio. If your testing infrastructure is relatively mature, you will ideally have a mobile test management tool at the center. That will need to talk to and share information with every other core system you use, which will increase visibility of your whole quality process and create multiple efficiencies.

Get in touch with us to see how we can help increase your regression testing efficiency and the efficiency of your whole QA and quality operation.

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

 

Try QMetry Total Test Management for Free

30 Day Free trial. Test Management made simple.