Python Measure Unit Test Action

[jslane-h]

• Action to run tests on Python measures
• Fixed bug in GenerateConStrainReport measure

[lymereJ]

Looks good!

@jslane-h - Could we perhaps also run a measure check using the openstudio measure -t <path/to/lib/measures> after installing openstudio with pip? I know that some error are expected but perhaps we could filter the ones that are expected and fail the build if other appears.

[jslane-h]

Looks good!

@jslane-h - Could we perhaps also run a measure check using the openstudio measure -t <path/to/lib/measures> after installing openstudio with pip? I know that some error are expected but perhaps we could filter the ones that are expected and fail the build if other appears.

It looks like the CLI isn't installed when pip installing openstudio. I tried manually installing openstudio and got an error that I'm guessing is due to its size. Using docker might be a good strategy here. Any suggestions?

[lymereJ]

@weilixu - should we always test using the latest version of OpenStudio?

[weilixu]

I am not sure - I guess it should depends on the measure dependency. If all measures move at the same pace, we can use the latest OS version for testing.

[jslane-h]

@lymereJ @weilixu I found a way to add an auto-commit if we run 'openstudio measure -t ...' and changes are made to the XML's. Would this be helpful?

I originally wanted to fail if changes are detected, but this ran into an issue with the python measure XMLs since <error>Failed to infer measure name from ...</error> depends on where the machine is storing the measure.