You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently test operators like in-range require hard coding values for the range test. Would like to see those values be able to be expressed as xpath searches within the existing document. An example of what I would like to be able to express:
optics_check:
- rpc: get-interface-optics-diagnostics-information
- iterate:
xpath: '/interface-information/physical-interface/optics-diagnostics'
id: '../name'
tests:
- in-range: ./laser-rx-optical-power, ./laser-rx-power-low-warn-threshold, ./laser-rx-power-high-warn-threshold
info: "Good: All laser receivers within warning thresholds."
err: "Interface {{post[../name]}} laser is receiving out of range at {{post[./laser-rx-optical-power]}}. "
The text was updated successfully, but these errors were encountered:
jnpr-bowen
changed the title
enhancement request: allow operators do not support comparisons values to be xpath searches
enhancement request: allow operators to support comparisons values as xpath searches
Mar 13, 2018
Currently test operators like in-range require hard coding values for the range test. Would like to see those values be able to be expressed as xpath searches within the existing document. An example of what I would like to be able to express:
The text was updated successfully, but these errors were encountered: