You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we really need to call executeDiagnostics() 4 times on 12 cohorts on each database platform? I would think calling 2 times (once to test iterative running) on 2 cohorts should be enough.
CohortDiagnostics is currently a bottleneck in creating a HADES-wide release, as its unit tests do not appear to complete ever on my machine.
The text was updated successfully, but these errors were encountered:
This is highly desirable but a large amount of work and suitable to pick up for a few developers interested in learning this package.
Ideally, we should test the functions of this package individually with isolated tests. At some point testing the entire pacakge was decided (probably to get unit test counts up).
Do we really need to call
executeDiagnostics()
4 times on 12 cohorts on each database platform? I would think calling 2 times (once to test iterative running) on 2 cohorts should be enough.CohortDiagnostics is currently a bottleneck in creating a HADES-wide release, as its unit tests do not appear to complete ever on my machine.
The text was updated successfully, but these errors were encountered: