Uploaded image for project: 'PBS Pro'
  1. PP-695

Enhanced approach to run or skip PTL tests based on various reasons

    Details

    • Type: User Story
    • Status: Open
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: PTL Framework
    • Labels:
      None
    • Story Points:
      1

      Description

      While PTL test execution, a PTL test can run or can be skipped based on various conditions like platform on which it is tested, PBS code that is being tested, combination of PBS features etc.

      Hence, we need an approach where the test writer gets options to specify his condition whether to run or skip the written test on combination of one or more such reasons.

      One of the approaches suggested is as below:

      Have a visitor pattern like “is_ok_to_run()” which is called by the framework before every PTL test is run. This needs to be defined by the test writer inside which he can specify various conditions and combinations of conditions that the result in true/false return value of is_ok_to_run() which is by default true if nothing is specified in its definition. These condition checks can be in terms of below APIs provided by the framework:
      Ex:
      am_i _on_cray()
      is_cray_build()
      is_cpuset_mom()
      is_multi_nic()
      is_power_enabled()

      So the writer can say conditions like below to run his test:
      if is_cpuset_mom() && is_power_enabled()
      return True

      We need to enhance and have such a better approach instead of the current approach of skip decorators provided by PTL: skipOnCray, skipOnCpuSet, checkModule etc.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              saritakh sarita kh
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: