Criteria	Usage
Questions with keyword1 or keyword2	keyword1 keyword2
Questions with a mandatory word, e.g. keyword2	keyword1 +keyword2
Questions excluding a word, e.g. keyword2	keyword1 -keyword2
Questions with a specific tag and keyword(s)	+[tag1] keyword1
Questions with two or more specific tags and keyword(s)	+[tag1] +[tag2] keyword1
To search for all posts by a user or all posts with a specific tag, start typing and choose from the suggestion list.

Article by Aharon.S · Feb 25, 2014 at 12:20 PM · Yaniv.K edited · Apr 25 at 11:26 PM

How to work with 'Update Local Tests' functionality

Job Queueing of local TestShell tests, controlled by Source Control (like SVN)

One of the features in TestShell is the ability to create and run the test suites in the Job Scheduling portal.

By default, when creating new test suites, the user can only select shared tests (tests which are stored on the TestShell database).

Note: Running local tests aimed mainly for accounts which use source control system in order to manage their TestShell tests

In order to select a test from a ‘Local folder’ some configurations are required.

First, let’s try to understand what would be the flow while working with local tests:

Each test developer creates and saves tests on his local machine – his local tests folder should be mapped to a source control repository which stores all of the tests.
A test developer completes a test development/modification and uploads it to the source control.
An admin can then execute an update process to make sure that all of the Execution Servers have the latest version of the tests, and that the portal is showing the latest version as well (changes might include new tests, new functions, new inputs, etc).

How does it work

After understating this main concept let's drill down to the technical part:

The 'Update local tests' button (available for admins only) runs a batch script file. This file retrieves the latest version from the repository to the TestShell server machine (the files on the TestShell server are used for listing only - and allows the Portal to show which tests exists/get inputs/etc.
Once the batch file finish running successfully:
- For each execution server – if the execution server state is idle (not running any test) - the execution server will launch a batch file which will retrieve the latest tests version to the execution server.
- During this update the execution server will not run any new job until the batch file ends successfully.

Configuration

For the latest information about the required configurations, please follow the instructions provided in the online help page which discusses Enabling Automation Suites to Use Local Tests.