This page appears in the PTL Developer's Guide.
Process for Improving PTL FrameworkThe process for improving the PTL framework is the same as the process you use for changing source code in PBS Professional. PTL Directory StructureConstruction of PTLPTL is derived from Python's unittest. PTL uses nose plugins. Testing PTLTests that test PTL are in pbspro/test/test/selftest, at https://github.com/PBSPro/pbspro/tree/master/test/tests/selftest Enhancing PTL for New PBS AttributesHow to Add a New Attribute to the LibraryThis section is for PBS developers who may be adding a new job, queue, server, or vnode attribute, and need to write tests that depend on their new attribute. PTL does not automatically generate mappings from API to CLI, so when adding new attributes, it is the responsibility of the test writer to define the attribute conversion in ptl/lib/pbs_api_to_cli.py. They must also define the new attribute in ptl/lib/pbs_ifl_mock.py so that the attribute name can be dereferenced if the SWIG wrapping was not performed.
ATTR_geometry: "W job_geometry="
ATTR_geometry: "job_geometry"
Nose Plugins for PTLRelated Links and ReferencesComplete Doxygenated PTL Documentationhttp://www.pbspro.org/ptldocs/ Repositoryhttps://github.com/PBSPro/pbspro Nose Documentationhttp://nose.readthedocs.io/en/latest/testing.html Python Documentation |