First, it is import to understand the difference between a Test and a Function.  Whenever a Suite is executed, all Tests are going to be run on all Execution Targets.  So, if you have 10 Tests and 2 Execution Targets ( eg. Firefox Browser and Android Chrome ) then it will run each test twice for a total of 20 executions.  Functions are only executed of that are called by a test using an Action such as Call.

Given the information above, a test can be disabled in one of two ways.

1. Open the settings of a test and change the Type to Function.  This will not allow the test to run but it will still generate the code and allow you to call it else where if needed.
2. The other is to assign tags to your tests.  Given the example above, you could add a RUN tag to all of your tests. You can remove that tag from a test and at execution time specify the RUN tag and only those test will execute.  For our standard templates, add '-t RUN' to specify the RUN tag.  If you are using alternate templates, please refer to the documentation of the template for any changes to the command line parameter set.

I hope that helps

cm