Our product team has been hard at work delivering new products and features for scaling test automation, increasing productivity and reporting across large-scale projects. Suffice it to say our test engineer and developer users asked, and we delivered.
That’s why this product release, we focused all our attention and love on the unsung heroes of the qTest Platform — the qTest administrators. Since they perform tasks that are critical to the workflows of testing teams – inviting new users, creating projects, adding custom profiles and granting product access- we wanted to give every qTest administrator a more streamlined experience with significant qTest administration enhancements.
qTest Administration Enhancements for a More Streamlined Admin Experience
Improved User Management Grid
Our new user management grid allows admins to manage users with ease with improved filtering capabilities, custom grid views and the ability to invite new users in bulk. This release also enables admins to quickly filter and sort users based on profile type, level of activation, authentication system and user profile type.
Batch User Management Capabilities
Our biggest enhancement is a big time-saver for administrators: The ability to perform various batch actions, such as adding new users to projects, deactivating or activating accounts, resetting passwords and adding users to a user group.
Better Product Accessibility With User Groups
Tricentis qTest offers quite a few products – which can be a double-edged sword for administrators who have to grant access and enforcement of which users get access to which products. With our new new user group feature, we are replacing the “Admin Profile” artifact so qTest administrators can bulk assign users to products and profile types.
For example, an administrator can now grant individual or multiple product access simply by creating a new group and assigning users to that group.
Private Value for Site Fields
qTest administrators are also responsible for setting up site level fields and templates for groups of projects. While site fields are crucial for project standardization, some projects need to have private values within the same template.
For example, if I have a site template for five projects and only three of those projects are using the Blocked status value for the Test Run Status field, the qTest admin can make the “Blocked” status a private value for these three projects. Another example would be to have a custom combo list for defect severity at the site template, but designate private list values (i.e. Sev 1, Crucial, High) to different projects. These private value feature allows the site template fields to remain the same but have the ability to designate private value for the field per project.
Batch Managing User Authentication
A simple but hotly requested feature relates to the ability to import XLS user lists to update authentication system information.
To learn more about the new qTest administration enhancements that are a part of the 9.3 release, read the release notes.