We used to have short release cycles in the past but haven’t published anything out since April 26th. I hope this version is worth the waiting especially for the wonderful users that asked for these features.
One of the common inquiry for Support team was “How can I arrange my Test cases / Requirement structure?” By default, you will see objects’ arranged ascending by created date on your navigation tree. With the new Re-ordering feature, you can drag & drop objects to re-arrange your test cases or requirements structure.
The major update that goes along with this is Customizable ID setting, you can define objects’ prefix and qTest will append the ID for the new created ones. The convention allows user to copy & paste objects with the same name, you will no longer see “Test case A” > “Test case A (1)” but the new ID and same name. We applied the following rules to retain your projects’ data:
Current Projects: ID will contains new prefix with number’s generated consecutively, continuing at existing ID number in qTest system regardless of object type.
New projects: ID number’s generated per project, counting from 1 for each object type, eg. RL-01, TC-01, or DF-01.
Have you been naming your objects with ID eg: 001 – Test case A, 002 – Test case B, we will provide a ID display toggle option in the next release to let you hide / show qTest ID if you prefer to use your convention. However we suggest qTest users to rename the objects and remove the “manual” ID and have qTest to handle the ID part.
The most anticipated feature that also based on the system ID is Tagging. Let say you want to mention the dependent requirements in your requirement, related defects on your defect description…etc., you can point to these objects by tagging the ID in the rich text field as following syntax:
Use “@ + object ID”, eg. @TC-622
Click to select the object ID in the dropdown list
The tagged ID will be shown as a hyperlink that leads you to tagged object
You will also find some minor improvements as the new Rich text editor in many places, we hope this function enhances users experience with requirement creating. Moving objects and table row in qTest’s now is flexible and “universal”: navigation tree, test steps, test runs table in test suite, field settings…
The last major upgrade is the Test case import wizard, it’s more a wizard now J. qTest will analyze your excel file:
Using the column of the first sheet as fields for mapping with Test case object’s properties.
Each sheet of the file will be imported as a Module in qTest. (*Microsoft Excel has 31 characters limitation for the sheet name, this will also limit the module name length when importing)
Test case ID will be populated by qTest at importing. If you map test case ID (in case you are importing a file exported from qTest), the system will update the online test cases that have the same ID with the local ones.
Simply drag and drop your available fields into qTest properties table below to complete the mapping wizard. (*if you have custom fields on your Excel file, please create the same fields on qTest prior to the import). Once the importing’s completed, qTest will present the result. You can review and made necessary editing in case the system finds conflict data.
Be patient if you have a large file, it may take up to 3 minutes for 300 test cases with around 20 steps per test case.
I want to thank you all, the users that give us valuable feedbacks. We are continuously fixing bugs and working on new features to make testing’s cooler and better. Please reach me at firstname.lastname@example.org if you have feedback or questions.