Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata


This plugin allows you to choose specific tests you want to run.

Plugin Information

View Tests Selector on the plugin site for more information.

User guide

Enabling The Plugin In Your Job

  1. Navigate to the Job configuration page.
  2. Choose the checkbox This build is parameterized.
  3. Click on Add Parameter drop-down list.
  4. Select Choosing Tests.


Filling The Parameters

  1. Specify the name of the environment variable in which you want your selected tests to be saved in. 
    After build the selected tests will be in this environment variable as a JSON array.
  2. Enter the properties file path (see more information bellow).
  3. Add a description (optional).

About The Properties File

This file will contain all your tests and (maybe) some extra fields for the plugin.

Your properties file MUST have a property called tests.
The tests property value is a JSON array that contains a JSON object for each test. 
In each test object you need to specify it's attributes by a key/value pairs.
The following properties will allow you to select specific fields which have a special meaning:


The name of the field that will imply if the test is enabled or not.
If the value in the specified field, for some test(s), will be false then the test will not be shown at all.


The field that the plugin will group the tests by.
If 2 tests have the same value in this field, they will be in the same group.


The field(s) that will be shown in the tests tree.


The field that will be set to the amount of times the test should run.


The character that will separate between the fields in the tests tree.

All fields are case-sensitive.
Each property must be defined either in the properties file OR in the override section. 
If you want to change the properties you defined in the file, you can override them in the override section.

This is an example for a properties file which contains all above properties:



Override Section

In this section you can override the properties you defined in the properties file or define them for the first time.
If you want the override to be done you must check the appropriate checkbox.
If you click on the Fetch properties From File button it will fill the properties bellow from the properties file above.

If you click on the Show/Hide Available Fields button it will show/hide all the fields used in the tests you defined in the properties file. 
In Show Fields section, Next to each Available field appears (howManyTestsHasThisField/amountOfTests).
Multiplicity Field can exist in some (all) of the tests.

After clicking on Build Now button you will need to choose the tests (organized as a tree).
For each test you chose, you will need to fill the amount of times you want it to run.

Clicking on Build button will continue the build with the tests as your parameter (in the environment variable you chose). 


  1. Unknown User (andrewsumner)

    Any chance that you could add a couple of changes along with configuration settings to enable?

    1. Hide multiplicityField - I only want users to run tests once
    2. Select single tests mode - Hide select/unselect buttons and only have checkbox available on test node, not parent folders

    I'm after a way to allow users to select and run a single test (we're using junit and concordion) and this is the nicest option I've seen so far.

  2. Unknown User (durga_patro)

    I am trying to run selected tests with the Tests Selector Plugin for Jenkins. I followed the tutorial in the wiki.When I build the project I can see the tests in a Tree structure. Here I have selected the checkbox for few tests and for other I have kept the checkbox unchecked.

    But when the build starts, it executed all the tests present in the test set folder including the ones which I have not selected.

    Can anyone please help me?