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
Make meteonorm remote_data tests robust to data changes (#2810)
The meteonorm iotools tests pinned specific values, the full column
list, and exact column counts returned by the live API. Meteonorm
regularly updates their weather dataset and adds parameters to the
'all' set, neither of which is a breaking API change, but both cause
these tests to fail spuriously (e.g. new
'surface_tilt'/'surface_azimuth'
columns broke the exact-list assertion).
Assert only what pvlib controls, not what meteonorm's dataset controls:
- realtime: check the known columns are a subset of the response and
that the column count is at least as large, instead of exact equality.
- training/tmy: drop the golden-value assert_frame_equal comparisons
(and their fixtures); check columns, numeric dtype, and that at most
20% of values are NaN (the guarantee meteonorm provides).
Row counts and index checks are kept since they are determined by the
requested time range, not the dataset.
0 commit comments