Any JUnit test class can access a test parameter of the underlying test as a Java system property; the launcher passes these
               parameters to the executing machine using the "-D" VM argument. 
               	 
            
 
            	 
            In addition to the customer-defined parameters , you can always call the following Java system properties from a JUnit test:
               
               	 
               
 
                  		   
                  			 
                  - Parameter 
                        			 
- Description 
                        			 
- #sctm_execdef_name 
                     			 
                  
- The name of the execution plan that is currently executed. If the execution was triggered from the 
                     				Tests area, the parameter has the value 
                     				Unassigned Tests. 
                     			 
                  
-  #sctm_execdef_id 
                     			 
                  
-  The numeric identifier (database key) of the execution plan that is currently executed. 
                     			 
                  
- #sctm_product 
                     			 
                  
-  The name of the product as defined in the executed test container. 
                     			 
                  
- #sctm_version 
                     			 
                  
- The name of the version to which the results of the execution are associated. 
                     			 
                  
- #sctm_build 
                     			 
                  
- The name of the version to which the results of the execution are associated. 
                     			 
                  
- #sctm_keywords 
                     			 
                  
-  A comma separated list which contains the keywords that are defined for this execution plan. 
                     			 
                  
- #sctm_regular_execdef_run_id
                     			 
                  
-  The numeric identifier (database key) of the regular execution plan run. For setup and cleanup tests this property contains
                     the run ID of the regular run.
                     			 
                  
- #sctm_test_results_dir 
                     			 
                  
- The path of the directory where the result files of the test reside. 
                     			 
                  
- #sctm_test_name 
                     			 
                  
- The name of the 
                     				Silk Central test being executed. 
                     			 
                  
- #sctm_test_id 
                     			 
                  
- The numeric identifier (database key) of the test being executed. 
                     			 
                  
- #sctm_source_root_dir 
                     			 
                  
- The local path of the test container's root directory, where all files under version-control reside. 
                     			 
                  
- #external_id 
                     			 
                  
- The unique identifier of a test case in a test package to be executed. You can use this as a filter if only specific test
                     cases in a test package should be executed. 
                     				
                      
                        				
                      
- #is_test_package_root 
                     			 
                  
- If 
                     				true, the test being executed is the root node of the test package (default). If 
                     				false, only specific test cases in a test package specified by 
                     				#external_id are executed 
                     			 
                  
- #sctm_data_driven_parent_test_name 
                     			 
                  
- The name of the parent test, if the executed test is a data driven row. 
                     			 
                  
- #sctm_data_driven_parent_test_id 
                     			 
                  
- The numeric identifier (database key) of the parent test, if the executed test is a data driven row.