QMetry 6 updates the industry’s leading Agile QA management tool with a series of improvements designed to solve the most difficult enterprise quality assurance problems. Starting with improved enterprise level administration that lets teams start up quickly. QMetry’s enhanced import and integration user interface also allows teams to start up fast and ensure that all their existing assets and tools can be quickly integrated into an improved QA process. QMetry comes with a large feature set, but the most important part of the design of QMetry 6 was to focus on solving the problems that face QA most.
New User Experience
A New Desktop Experience that makes multitasking easy. Like the desktop views that everyone are already familiar with our desktop has a Start Menu and Task Bar that makes navigating the interface easy for both new users and existing QMetry 5 users. Early trials have shown that even existing QMetry 5 users adjust quickly to the new interface.
The Module Toolbar in now optional which means you have more working space. In fact there are many small changes including improvements to the menu bar and the ability to maximize any windows that provides much better support for lower resolutions in QMetry 6.
QMetry 6 also Simplified the Toolbars and removed the confusing mix of toolbars and tabs. The new UI provides one even User Experience for all modules and makes it easier for users to learn how to use the software. The toolbars have also been optimized to fit in lower resolutions, and take up less space allowing more screen real estate for the information that matters. The toolbars on the tree have been simplified and covers 1 row inline with headers of the grid.
The Scope is now at the top and the window and clearly applies to both panes rather than its odd placement above the tree. To the right on the same toolbar is the new search button which makes it much easier to find your assets. The improve save search feature also makes it easy for users to create a search that can be used repeatedly to find common issues for each new development cycle.
The grid has also been improved with the use of icons in the header to conserve space, an addition of an ID column, and a new Save and Manage Views feature which allows users to create their own view of the grid that best suits their needs.
The new Add Button is easier to find and combines a number of user friendly options. The ability to add an asset based on another asset has been enhanced with new options. For instance updates to the database now allow us to automatically map fields from one module to another. So when creating Test Cases from Requirements all fields can be mapped- including custom fields! (note: This mapping also works when import from external systems like JIRA and Rally). This means less information is lost, and without users having to manual enter redundant data.
Another improved button is the Scope Button. Most users will want to add or remove from current scope. This has been made easy, no pop up needed. Adding to other scope, less rarely used, has been given a new user friendly UI. And the functionality of scope button has been unified across modules.
New Asset View
Viewing assets has been improved with the new Asset Details Page which allows you to see all the important information in one compact view. Rather than having to click on multiple tabs to see the linked assets, attachments execution history, or activity/change history users can see everything without loosing their place. Small improvements like the improved multi-select fields, and a more compact rich text field helps users see more of what they need in one view. Limitations on the number of rich text fields, and custom fields have also been removed.
User Story: Customers that reuse test cases often can now better use the Test Case Details page as its own report showing the Test Case details, execution history, attachments, associated defects all at one time.
Editing an asset has also been improved. You can now expand the test case step section to fill the whole screen. This allows teams that use a large number of steps see more steps in one view. This also helps in editing test cases with lots of text.
The New Rich Text Editor gives plenty of space to edit and makes adding and editing steps super user friendly. With the new interface users do not need to touch their mouse to move from field to field, making it as easy to edit rich text like they would any field in an excel spreadsheet- unlike Excel they have far more space to work with, and far more freedom to use different types of rich text. Rich text even allows users to view and edit in raw HTML making advanced use of code snippets easy to support.
Improvements to Platforms
The ability to support multiple platform and configurations has taken a huge leap forward. Enterprise users can easily create groups of similar platforms (e.g. Mobile devices, test beds, browsers, etc.). The groups will have common attributes with shared or unique values for each separate platforms. Attributes are now like any othercustom field allowing organizations to create any field type (e.g. string, multi-select, numeric, etc.) and assign them to one or more platform groups.
User Story: For example a Mobile organization can create a group for Android and quickly create a lab of 100 devices, multiple OS versions, and multiple carriers. The QA group starts testing using the devices in the lab, and the management will now automatically be able to see reports showing the coverage matrix to see things as specific as test results of the UI using a specific resolution or hardware vs software keyboard, and adjust which devices to test based on these results.
User Story: This allows you to review preconditions or other instructions that might relate to the entire suite helping companies who need to record preconditions before testing gets started- start with a clean OS install, or conversely load X, Y, and Z applications before starting.
Do you have variables that change and need to be recorded at runtime? Perhaps you need to record the ambient temperature, change the applications installed on a device, or adjust the CPU utilization. No problem, QMetry allows you to adjust and Record Attributes at Runtime- you can even make it mandatory to force the tester to record the attribute to ensure that it is not forgotten. And all attributes are automatically recorded at the time of test so they can be later filtered in your reports! Not only is it easier to add new platforms, but we also will allow you to add run time attributes.
User Story: Run time attributes would allow you to change things like hardware or software settings that may vary from test to test on a platform (for instance a firmware or a OS / patch version). This will allow you to have one flexible platform that can cover many scenarios, and when looking at results the reports will allow to filter out by these attributes (e.g. All results of a iPhone 4 with iOS5 only).
This combined with our existing drops feature allows you more flexibility for continuous testing throughout your testing cycle.
QMetry’s new Custom Reporting Engine in Version 6 has over 100 pre-built queries and reports each of which can be added to the over 30 pre-defined dashboards. And if the over 40 reports don’t offer you the view of your testing that you are looking for you can create a new report using any query picking the field(s) that you want to group by and the report type to display it.
QMetry Classic had a limited Dashboard with 24 total reports (9 Cycle, 5 Release; and 10 Domain level reports). These dashboards were limited to either a donut, bar chart, or line graph formats. The new QMetry Report Engine has more than 3 times the chart types: Donut; Pie; Clustered Bar (Clustered); Bar (Stacked); Column; Column (Clustered); Column (Stacked); Line; Line (Marked / Multi-line); and Area.
All charts can be customized so that you can group by different fields (e.g. instead of grouping test case executions by testing status you could change the group by to see if your team is executing test cases by priority,component, etc). Charts can now also be filtered by any of a the fields in the table (e.g. If you are viewing the Test Case Execution History you can filter it by priority, test case type, folders, state, platform, etc. etc.). You can even filter by multiple fields at once!
QMetry’s has also improved our advanced Enterprise reports. Both the Build Report and the Coverage StatusReport have a much cleaner user inteface and and the export has been improved to allow a better view of the data.
Still not enough? Try creating your own query. QMetry 5 allowed users to create queries, but now every query you create can be converted into a report!
There is no doubt- QMetry 6 provides the most reporting options of any QA tool, and provides the most robust options to analyze your testing to make that go or no go decision to launch.
There are some exciting changes in the Admin as well. All the System settings have been moved into admin including the manage roles which is really a system level setting. Administration just got a lot easier with all settings part of one unified interface. User management has been improved to include new user fields including LDAP groups, locations, titles, and a flexible tag option. The user list can be easily filtered by any field to easily find users and assign them to domains either individually or in groups.
We have also improved the permission levels including a new permission for integrations.
The user management has been much improved with the addition of new fields for LDAP groups, Locations, Titles, and a flexible “Tags” field. With a new interface that allows admins to filter users by any field and make bulk changes Admins can quickly update their users roles and permissions.
User Story: One Enterprise customer regularly needed to maintain a user base of 1000+ users. In the old interface if they needed to add 100 users to 10 projects using 5 different roles they would need to make 1000 independent actions. Using the new Admin module they can quickly import users and bulk join each group in 5 steps or less.
In QMetry 6 Domains now have keys to allow QMetry assets to be easily referenced. All the features of the custom fields (aka User Defined Fields (UDF)) are now in Admin including archiving, locking, and cloning. Custom Field Management is also easier.
All fields are global and can be assigned to any or all modules. This allows common fields between modules and even domains to be mapped to allow easy migration of data from one module or domain to another. Since all custom fields are now common to all domains, organizations will find it easier to add new domains with all the custom fields that an organization has already setup. This also makes copying assets with all fields from one domain to another a breeze.
Mapping fields across modules and with external integrations is now much easier. Since field are common to all modules, it is now possible to copy the data from even custom fields from issues, to requirements to test cases! The new field mapping also allows easy mapping of QMetry Fields to external tools such as JIRA, Rally, FogBugz, etc. And to make it even easier QMetry provides auto mapping for each integrations’ system fields.
QMetry 6 comes with an internal issue tracker that remains in sync with your main issue tracker. The QMetry Issue tracker is not provided as a replacement to your existing best of breed tool; however, its inclusion provides new power in reporting possibilities. It can also save time in reviewing and updating the status of issues in development.
The Issues Module has common UI/UX as the other QMetry modules making it easy to navigate for the QA testers. One key difference is that issues are organized by groups instead of folders. This allows for improved quick filtering compared to other tools. (Note: The Issue Module does not come with the unnecessary folder system that does not fit well with the workflow of issue tracking). As with the other modules you can save your views and with issue tracking you can save different types of groups.