• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

MITLibraries / timdex-dataset-api / 16910973457

12 Aug 2025 01:48PM UTC coverage: 93.089% (-1.7%) from 94.828%
16910973457

Pull #161

github

ghukill
First pass at reinstating all tests

Why these changes are being introduced:

During the refactor to use dataset metadata for querying,
we had to temporarily skip tests that tested for dataset
filtering and current records limiting.  With the SQL backed
querying now in place, these tests can be reinstated.

Note that a future commit will likely *add* a couple more
tests for the new, optional 'WHERE' clause functionality.

How this addresses that need:
* No tests are skipped.
* Dataset filtering tests still remain, but the key/value
filters are just handled differently under the hood.
* Tests for current records no longer use
.load(current_records=True) but instead utilize the
DuckDB table via table='current_records' within a
read method.

Side effects of this change:
* None

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/TIMX-529
Pull Request #161: TIMX 529 - read methods utilize SQL + metadata context

116 of 130 new or added lines in 4 files covered. (89.23%)

458 of 492 relevant lines covered (93.09%)

0.93 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

89.11
/timdex_dataset_api/utils.py


Source Not Available

STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc