Search via the context menu
In Tosca Commander you can perform a search for objects and their properties directly via the context menu. The available search parameters vary depending on the selected object. You can also select more than one object.
To start the search, select Search all from the context menu of an object and select the required parameters from the next menu level.
Procedure
-
Select the object in the workspace, from which a search query should be started.
-
Select Search all from the context menu and select the desired parameter.
-
The query is started as a TQL Search (see chapter "TQL Search").
Options
Tosca offers the following search parameters in single-user workspaces by default:
Search all |
Description |
attached files |
All file references are searched. |
References |
All objects and groups that are directly linked to an object are searched. |
Lost Objects |
All objects that no longer have a valid position in the Repository are searched. |
ExecutionEntries |
All ExecutionEntries of the ExecutionLists are searched. |
ExecutionEntries: no Result |
All ExecutionEntries with the value no result are searched. |
ExecutionEntries: Failed |
All ExecutionEntries with the value failed are searched. |
ExecutionEntries: Passed |
All ExecutionEntries with the value passed are searched. |
ExecutionLists |
All ExecutionLists within the selected ExecutionEntry folder are searched. |
Not assigned Teststeps |
All TestSteps not assigned to any Module are searched. |
Not assigned Teststepvalues |
All TestStepValues not assigned to any ModuleAttribute are searched. |
Disabled Testcase-Items |
All disabled TestCase Items are searched. |
Usages |
All referenced usages of an object are searched. |
Used Modules |
All used Modules of an object are searched. |
Used XModules |
All used XModules of an object are searched. |
Ambiguously named ObjectMaps |
All ObjectMaps are searched and listed which do not have a unique name. The search window is opened (see chapter "Editing the search results") |
Tables with specialized Ktx |
All table attributes are searched which have a specialized Ktx parameter. |
TestSteps with VirtualTestStepValues |
All TestSteps containing a virtual TestStepValue, corresponding to the chosen ModuleAttribute, are shown. |
synchronized folders |
All synchronous ExecutionEntry folders in an ExecutionList are searched. |
Objects with virtual TestStepValues |
All objects are searched, which have only initially created XTestStepValues for the selected XModuleAttribute. |
TestStepValues with virtual TestStepSubValues |
All TestSteps, which contain a virtual TestStepSubValue that in turn is based on the selected customized control of an attribute (e.g. an attribute of a table), are displayed. |
In multi-user workspaces the following search queries are also available:
Search all |
Description |
CheckedOut Objects (by me) |
All objects checked out by the current user in the local workspace are searched. |
Changeable Objects |
All changeable objects (checked out by the user) are searched. |
Used OwnedItems |
All used, assigned objects are searched, e.g. all Modules, which are referenced in the TestSteps of a TestCase, represent used OwnedItems. In the case of ExecutionLists this would apply to all the TestCases used in the ExecutionEntries (and as a consequence all Modules used in the TestCases). |
Excluded Objects |
All objects that are excluded from synchronization are searched |
Used OwnedItems (checked out by me) |
All used, assigned objects checked out by the current user are searched. |
Used OwnedItems (checked out elsewhere) |
All used, assigned objects checked out by other users are searched. |
The following search options are additionally available to administrators:
Search all |
Description |
CheckedOut Objects (all users) |
All objects checked out by all users are searched. |
Users with CheckedOut Objects |
All users with checked out objects are searched. |
The following options are available for the Tosca Requirements Management:
Search all... |
Description |
Linked TestCases |
Any TestCases are listed that are linked with a Requirement. |
Leaf Requirements |
All Requirements which are in the bottommost hierarchical level are searched - starting from a RequirementSet or a Requirement. |
Usages as linked RequirementSet |
Searches for all linked usages of the RequirementSet. |
The following options are available for TestCase-Design objects:
Search all... |
Description |
Attached Files |
Searches for all file references. |
Datasource usages |
Searches for all TestCase TemplateInstances that use the TestSheet or the class as a data source, starting from a TestSheet or a class. All TestCases which use the TestCase-Design instance as a data source, are searched for, starting from a TestCase-Design instance. |
Filtered Instances |
Searches for all instances a filter has been applied to (see chapter "Filter Instances"). |
References |
Searches for all objects and groups directly related to an object. |
Schemasource usages |
Searches for all TestCase Templates which use the selected TestSheet as a schema. |
Linked Requirements |
All linked requirements are searched for, starting from the selected TestCase-Design instance. |
Usages |
Searches for all referenced usages of the selected object. |