Skip to content

test: OneLibrary adapter fixture stores lengths in seconds (NP3-414) - #11

Merged
chrisle merged 1 commit into
mainfrom
fix/NP3-414-onelibrary-seconds
Sep 26, 2026
Merged

chrisle merged 1 commit into
mainfrom
fix/NP3-414-onelibrary-seconds

Conversation

@chrisle

@chrisle chrisle commented Sep 26, 2026

Copy link
Copy Markdown
Owner

onelibrary-connect 1.1.6 (chrisle/onelibrary-connect#1) reads content.length as whole seconds, the unit rekordbox writes: three real exportLibrary.db exports read 195, 390, 297 for normal tracks. This repo's copy of the adapter spec still built its fixture in milliseconds and expected ÷1000. The publish job checks out onelibrary-connect at main, so publish run 36256252752 failed at Run tests.

  • create-test-db.ts and the committed test-onelibrary.db now store 300/240/180/210/225 seconds
  • The duration assertions check the stored value

Local: jest 504 passed (37 suites) against onelibrary-connect main.

…e real exports, so the publish passes again

- Rewrite the fixture's content.length values from milliseconds to seconds, in both create-test-db.ts and the committed test-onelibrary.db
- Assert durations as stored, matching onelibrary-connect 1.1.6
@chrisle
chrisle merged commit 8e34fbf into main Sep 26, 2026
3 checks passed
@chrisle
chrisle deleted the fix/NP3-414-onelibrary-seconds branch September 26, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant