Versions Compared

Old Version 7

changes.mady.by.user Shilpa Kodli

Saved on

compared with

New Version 8

changes.mady.by.user Shilpa Kodli

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Description

Currently, PTL doesn't support running test case from non-test dircetory directory using pbs-benchpress TestExecution option ('-t') i.e. a directory where all tests exist.

...

This design document is to support pbs_benchpress to execute test cases(or testsuite test suite by it's class name) from any directory on the host apart from tests directory.

...

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 PTLTestLoader

Interface : PTLTESTS  PTL_TESTS_DIR

Detailed explainaion explanation 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 dircetorydirectory, if it doesn't find then it will search in PTL installed dircetory directory (Ex: /opt/ptl/tests)
  2. User can also specify path to tests dircetory directory it is not present in PTL installed directory. If user wish to place tests in some non-default dircetory directory, then user can mention using environment variable "PTLTESTSPTL_TESTS_DIR".                        Ex: export PTLTESTSPTL_TESTS_DIR=/home/user/temp/tests"
  3. If PTLTESTS PTL_TESTS_DIR is mentioned, then PTL will serach in PTLTESTS dircetory search in PTL_TESTS_DIR directory only when it doesn't find test case in current and PTL installed directory.
  4. Currently PTLTESTS PTL_TESTS_DIR is limited to single path specification. We can mention PTLTESTS PTL_TESTS_DIR to point to single path.

Currently PTL supports getting test info only from tests directory. Now, one can get test info using pbs_benchpress INFO option (pbs_benchpress -i TestSuitName) from any dircetory directory apart from test dircetorydirectory.


Example:

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

...

Consider running a single test case using pbs_benchpress -t option from /home/user/ dircetorydirectory(non-test dircetorydirectory) as pbsroot. 

  • pbs_benchpress -t SmokeTest.test_submit_job

Since, pbs_benchpress is run from /home/user/ path, it tries to find test case in current dircetorydirectory, when it fails to find then it will search in "/opt/ptl/tests/" and runs the test case successfully as it is present in "/opt/ptl/tests/".

Scenario-2:

Assuming tests dircetory directory is moved to "/tmp/tests/" path.

User need to export "PTLTESTSPTL_TESTS_DIR" environment variable to above mentioned path.

  • export

...

  • PTL_TESTS_DIR=/tmp/tests

Consider running a single test case using pbs_benchpress -t option from /home/user/ dircetory directory as pbsroot.

  • pbs_benchpress -t SmokeTest.test_submit_job

PTL first tries to find test case in current dircetorydirectory, when it fails to find then it will search in "/opt/ptl/tests/" path. If it fails to find there as well then it will search in user defined path given in environment variable "PTLTESTSPTL_TESTS_DIR".

Since, test case is present in path mnetioned mentioned in "PTLTESTSPTL_TESTS_DIR", test case runs successfully.

Scenario-3:

Assuming tests dircetory directory is moved to "/tmp/tests/" path and user has not set PTLTESTS PTL_TESTS_DIR env variable.

In this case when a test case is executed from /home/user directory, PTL throws error saying "Unknown testcase" as it fails to find the test case in current dircetory directory as well as in PTL installed directory which is "/opt/ptl/tests/"

OSS Site Map

Project Documentation Main Page

...