This was inspired from discussions following the SQA audit...
[ ] document how test skipping works in dev docs
[ ] develop and implement process for managing skip rationale(s) text
[ ] develop process to review/address skips on periodic basis
[ ] ensure skip info is included with release testing artifacts
[ ] There are various forms skipping a test to consider. One is just skipping the answer comparison but doing all the execution to get the answer. That is apparently what currently happens when individual tests in a .py file are skipped. The only way to skip actual execution associated with a test is to skip the entire.py file. Both are probably useful and this nuance should, minimally, be documented.
Schedule a skip list hackathon to get our bearings on what is on the skip list and if it should remain as such. Maybe we'll decide to remove the skip list entirely, or just pare it down significantly.
This was inspired from discussions following the SQA audit...
.py
file are skipped. The only way to skip actual execution associated with a test is to skip the entire.py
file. Both are probably useful and this nuance should, minimally, be documented.