The purpose of this PR was simply to create a pattern for unit testing code in workflows. It extracted some (fairly simple) code in the nightly product functional testing, created standalone files with that code, called that code from workflow, created unit tests for those files, and then created a new workflow that runs the unit tests. As this was successful, this is the pattern that will be followed for unit testing all workflow code; in particular, it will be used to improve the quality of the deployment code.
💠Motivation and context
Closes: #1164
🧪 Testing
Created code, tests, and workflows
Ran unit tests by hand and by workflow and by CI/CD pipeline
✅ Pre-approval checklist
[x] This PR has an informative and human-readable title.
[x] PR targets the correct parent branch (e.g., main or release-name) for merge.
[x] Changes are limited to a single goal - eschew scope creep!
Mostly. I did delete one random Markdown file that was incorporated into Nanda's testing README but hadn't been deleted.
[x] Changes are sized such that they do not touch excessive number of files.
🗣 Description
The purpose of this PR was simply to create a pattern for unit testing code in workflows. It extracted some (fairly simple) code in the nightly product functional testing, created standalone files with that code, called that code from workflow, created unit tests for those files, and then created a new workflow that runs the unit tests. As this was successful, this is the pattern that will be followed for unit testing all workflow code; in particular, it will be used to improve the quality of the deployment code.
💠Motivation and context
Closes: #1164
🧪 Testing
✅ Pre-approval checklist
Mostly. I did delete one random Markdown file that was incorporated into Nanda's testing README but hadn't been deleted.
✅ Pre-merge checklist
✅ Post-merge checklist