8.8 Searching Function

You can quickly search for a system object (including requirement, test case, test run, or defect) or piece of information that belongs to a system object (such as description or comment) by entering key words into the Search box located on the top right corner of any page.

Snap_2013-06-07_at_13.44.10.png

qTest supports both: free-text search and syntax search.

»Free-Text Search

»Syntax Search

Free-Text Search

System will search for free-text you input, and return all objects' fields containing that free-text, including:

  • Release: ID, Name, Status, Description, Release Note
  • Build: ID, Name, Status, Build Note
  • Requirement: ID, Name, Status, Description, Type, Comment
  • Test Case: ID, Name, Description, Status, Type, Test Step Description, Test Step Expected Result, Comment
  • Test Suite: ID, Name, Description, Execution Type
  • Defect: ID, Summary, Description, Status, Type, Comment
  • Test Run: ID, Name, Status, Execution Type, Test Step Description, Test Step Expected Result, Test Step Actual Result

button-round-warning-icon.pngHINT:

  • You can put a group of words between double quotes “…” to perform a search for exact phrase search. Furthermore, you can use the operators AND/OR and grouping ( ) in your search string.
  • Fuzzy search and wildcard search have been already implemented into free text searching. It means you don’t need to use * or ~ to perform these search technique.
    e.g.: enter “Test cause” will return “Test case” if there is no exact term of “Test cause” to be found in your project.
  • All custom fields can be configured to be searchable with Free-Text

Syntax Search

  1. Search by IDs

    Each qTest artifact is associated with an ID (including a prefix and an ID number) to help users refer to particular artifact(s) correctly as well as search for them quickly. To search for any object using their IDs, simply use the following syntaxes:

    a. id:id_number

    • Using this syntax this will return all objects which have the specified ID number.
      e.g: id:750 will return all objects which have ID numbers as 750 such as requirement RQ-750, defect DF-750, test case TC-750, etc.

    b. id:prefix id_number (This is also equivalent to: obj: object_type id:id_number)

    • If you specify your search a bit more with the object prefixes (RQ, TC, DF, etc..), using these syntaxes will return all objects of the specified type and ID number.
      e.g. id:tc-750 or obj:tc id:750 will commonly return the test case TC-750.
  2. Combining different search keywords

    You can also narrow down your search results by using a more advanced syntax search, which is generally made of the following attributes:
    obj:object_type object_field: free text AND/OR ( ) obj:object_type object_field: free text

    • obj is the keyword to indicate that you would like to search by a specific object
    • object_type is used to indicate the exact type of object you want to search.
    • object_field is used to indicate the exact field of an object you want to search.
    • colon “:” is required between object and object_name, search_field, and token

    The table below lists out all default search keys that are available for syntax search, you can freely edit them using the Field Settings feature (Refer to Project Settings-Field Settings)
    *All keywords are case insensitive

    Objects Object_ type search keys
    Object_field Object_field search keys
    Release rls Name name
        Status stat
        Description des
        Release note note
           
    Build bld Name name
        Status stat
        Build note note
           
    Test Case tc Name name
        Description des
        Status stat
        Type type
        Comment cmt
        Test Step Description tsdes
        Test Step Expected Result tsexp
           
    Requirement req Name name
        Description des
        Status stat
        Priority prt
        Type type
        Comment cmt
           
    Test Suite ts Name name
        Description des
        Execution type type
           
    Test Run tr Name name
        Status stat
        Execution Type type
        Test Step Description tsdes
        Test Step Expected Result tsexp
        Test Step Actual Result tsact
           
    Defect df Summary sum
        Description des
        Severity svt
        Priority prt
        Status stat
        Type type
        Comment cmt
  3. Search for Requirements imported from external system

    You can search for synced Requirements using the following syntax:

    • external:free text

    System will return the synced Requirements whose names or displayed external properties contain the input text.

button-round-warning-icon.pngHINT:

  • All keywords listed above are particularly preserved for syntax search. You cannot perform free text search using the preserved keywords.
  • Double quote “…”, operators AND/OR and grouping ( ) can also be utilized
    e.g.: (obj:tc des:“hello word”) OR (obj:req cmt:“new release” AND des:“ new update”).
    This syntax will return all test case(s) which have “hello word” in there description along with any requirement(s) which have “new release” in comment and “new update” in description.