November 29th Meeting #11
elimillera
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Present:
Eric Milliman
Marie Vendettuoli
Eli Miller
Eli - We ran into an issue when actually testing the SystemValidation Process. It ending up taking upwards of 10hrs to run the validation. That is way to long for a pipeline, we would want to aim for 15 minutes. To solve this I think we should pivot to using valtools as an infrastructure. The dependency issues I was concerned about was overblown.
Eric - Ideally we should have one central repositories of tests and update it regularly. I think that would be easiest for smaller companies to just pull down one repository.
Marie - It sounds like if we go down this path for tests for multiple packages We would have to think about how other users could be selective about the packages we test. How could a user only test the packages they need? Valtools has a way to subset the files in the yaml.
Eric - That sounds perfect. We could write some static analyzer and check projects. Why would valtools be faster than the original IQ/OQ.
Eli - The issue is that the original process runs the examples, vignettes, and tests for each package and when dplyr has three dozen dependancies the time starts ballooning.
Eric - I don't know if I could get that by some QA departments. Some of them want you to test everything and demarcate them and you can't do that in this process. I think this modularity is good though so we can do both ways. I think making this repository with all the tests and having people drop them is a good way to go.
Beta Was this translation helpful? Give feedback.
All reactions