libplist/test, branch 2.8.1

plist: fix the (sec, usec) date API round trip

2026-11-06T09:29:06+00:00

plist_set_date_val stores val = sec + usec / 1000000, but
plist_get_date_val splits it with a truncating cast and fabs():

    *sec  = (int32_t)val;
    val   = fabs((val - (int64_t)val) * 1000000);
    *usec = (int32_t)val;

Two results are wrong. The product is truncated, so set(5, 6) reads
back as (5, 5) - 29.3% of round trips over sec in [0, 3] come back a
microsecond short. And for a negative value, truncation toward zero
plus fabs() give a pair that does not denote the same instant:
set(-3, 250000) stores -2.75 and reads back as (-2, 750000), which the
setter would store as -1.25. Every round trip with sec < 0 and
usec != 0 is wrong.

(int32_t)val is also undefined when the stored value is outside the
int32_t range.

Round the seconds down, round the fraction to microseconds carrying
1000000 into the seconds, and clamp the seconds before converting, so
sec + usec / 1000000 == val to the microsecond with 0 <= usec <
1000000 - the convention the setter uses.

Add test/date_val.c covering fixed cases and a sweep over sec in
[-2, 2]. It fails on an unmodified tree - set(5, 6), set(-3, 250000)
and set(-1, 1) all come back as different instants - and passes with
this change, with make check at 44/44.

Co-Authored-By: Claude Opus 5 
Claude-Session: https://claude.ai/code/session_01Arn4YaWtcQBDsQuJtyBmFP

test: Add binary plist parser behavior tests

2026-11-05T22:46:59+00:00

Build small binary plists in memory and check that arrays and dicts
parse correctly with 1, 2 and 3 byte object references, and that
strings, extended size markers and array/dict references extending
beyond the object data area into the offset table are rejected.

Co-Authored-By: Claude Opus 5.5

test: fix leak of iii in integer_set test

2026-11-05T10:59:00+00:00

Free the plist created for the test before exiting, which fixes a leak
reported by LeakSanitizer.

Co-authored-by: bg0d-droid <81825610+bg0d-droid@users.noreply.github.com>

plistutil: preserve binary data on Windows standard streams

2026-09-29T15:00:18+00:00

Fix fread() unused return values by actually handling errors

2026-04-10T10:21:17+00:00

xplist: Enforce single root value inside

2026-02-25T01:27:00+00:00

Ensure that XML property lists contain exactly one root value inside the  element and reject any additional value nodes before .

Add tests covering root value handling and nested CF$UID conversion behavior.

Co-authored-by: Sami Kortelainen 
Co-authored-by: Nikias Bassen

xplist: Improve robustness of XML text parsing and value conversion

2026-01-29T16:45:01+00:00

This change adds stricter validation for numeric and date nodes,
including full-input consumption, overflow/range checks, and rejection
of invalid floating-point values. Whitespace handling is clarified by
explicitly trimming trailing XML whitespace for value nodes.

test: Fix ostep-invalid-types test case

2025-12-05T20:33:24+00:00

test: fix operator error

2025-11-20T03:01:58+00:00

Otherwise test fail with error [: -neq: binary operator expected

Signed-off-by: Ankur Tyagi

test: use unique output file names across tests

2023-10-03T09:41:32+00:00

Without the change tests ran in parallel occasionally clobber outputs of
one another and fail as:

    $ make check -j16 VERBOSE=y
    ...
    FAIL: huge
    ==========
    Converting
    File ../test/data/5.plist is open
    PList XML parsing succeeded
    PList BIN writing succeeded
    PList BIN parsing succeeded
    PList XML writing succeeded
    Size of input and output is different
    Input size : 4292380
    Output size : 4305301
    Comparing
    PList parsing failed
    FAIL huge.test (exit status: 3)

Closes: https://github.com/libimobiledevice/libplist/issues/234#issuecomment-1743820556