Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Stack Documentation and UX, utils
-
Labels:None
-
Story Points:10
-
Team:Architecture
Description
Following the investigatory work into switching our Python test files to be compliant with pytest, whilst still using unittest, a tech note needs to be written explaining the required changes.
Attachments
Issue Links
- is triggered by
-
DM-3901 Update some tests to support nose and/or py.test
- Done
-
DM-5164 Tests in daf_persistence should skip properly
- Done
-
RFC-69 Refactor sconsUtils to enhance usability in CI
- Adopted
- is triggering
-
DM-5973 Update developer guide with pytest guidance
- Done
-
DM-5911 Fix circular references in Mapper objects
- Done
-
RFC-176 Add psutil to stack
- Implemented
- relates to
-
DM-5979 tests in testArgumentParser.py fail Jenkins run-rebuild on nfs
- Done
-
DM-4329 Coadd_utils tests should run and skip if afwdata is missing
- Done
-
DM-609 afw unit tests not built unless afwdata available
- Done
- links to
John Swinbank I am pretty happy with the testExecutables code. It's an easy drop in to most packages. Yes, sconsUtils would have to be taught to ignore anything that doesn't have .py suffix, else you'd run the tests twice. Maybe we could have a transition step where people can copy in the testExecutables.py file from utils and we just run tests twice. Then when every package has been modified we modify sconsUtils. afw will need to have a bespoke version of testExecutables.py in order to pass the arguments through to those two commands.
The alternative is a big bang ticket where we change every package to use testExecutables.py and fix sconsUtils simultaneously.