Page Comparison

Description

...

Forum discussion at : http://community.pbspro.org/t/enhancement-of-pbs-benchpress-to-run-from-non-tests-directory/1660

Details:

File : utils/plugins/ptl_test_loader.py

Class : PTLTestLoader

Interface : PTLTESTS

Detailed explainaion of how PTL searches for a test case when executed using Execution option (pbs_benchpress -t):

1. When a test case is run using "pbs_benhcpress Execution option -t" option, PTL will look for the test case in current dircetory, if it doesn't find then it will search in PTL installed dircetory (Ex: /opt/ptl/tests)
2. User can also specify path to tests dircetory it is not present in PTL installed directory. If user wish to place tests in some non-default dircetory then user can mention using environment variable "PTLTESTS".                        Ex: export PTLTESTS=/home/user/temp/tests"
3. If PTLTESTS is mentioned then PTL will serach in PTLTESTS dircetory only when it doesn't find test case in current and PTL installed directory.
4. Currently PTLTESTS is limited to single path specification. We can mention PTLTESTS to point to single path.

Currently PTL supports getting test info only from tests directory. Now, one can get test info using pbs_benhcpress benchpress INFO option ('pbs_benchpress -i ') is also now can be run TestSuitName) from any dircetory apart from tests dircetory. Approach is similar to "-t" option as explained abovetest dircetory.

Example:

Assuming PTL is installed in "/opt/ptl/" path and tests dircetory is present under "/opt/ptl/tests path".

...