andrew/libakgl
1
0
Fork 0
Code Issues 67 Pull Requests Actions Packages Projects Releases Wiki Activity

tests/tilemap.c: the draw path -- akgl_tilemap_draw, _draw_tileset, load_layer_image #9

New Issue
Open
opened 2026-08-02 18:32:49 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 18:32:49 -04:00
Collaborator
Copy Link

Source: TODO.md, "Remaining work" (at bbb7b8f)

src/tilemap.c is at 62% line coverage, up from 47%, because the bounds and leak
work needed the loaders driven rather than merely called. The drawing half is
what is left.

Cover akgl_tilemap_draw, akgl_tilemap_draw_tileset and
akgl_tilemap_load_layer_image.

Make it a counting test, not a stopwatch. A stub draw_texture backend that
records the rectangles it is handed, asserting exactly one blit per non-empty
visible cell -- the same pattern tests/game.c uses for the update counter. That
is the only shape that catches the boundary double-blit in the tileset scan,
which is invisible to a timer and mostly invisible on screen.

Files: tests/tilemap.c, src/tilemap.c

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md, "Remaining work" (at bbb7b8f) `src/tilemap.c` is at 62% line coverage, up from 47%, because the bounds and leak work needed the loaders driven rather than merely called. The drawing half is what is left. Cover `akgl_tilemap_draw`, `akgl_tilemap_draw_tileset` and `akgl_tilemap_load_layer_image`. **Make it a counting test, not a stopwatch.** A stub `draw_texture` backend that records the rectangles it is handed, asserting exactly one blit per non-empty visible cell -- the same pattern `tests/game.c` uses for the update counter. That is the only shape that catches the boundary double-blit in the tileset scan, which is invisible to a timer and mostly invisible on screen. **Files:** `tests/tilemap.c`, `src/tilemap.c` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.9.x milestone 2026-08-02 18:32:49 -04:00
tachikoma added the test-coverageblast-radius:medium labels 2026-08-02 18:32:49 -04:00
tachikoma added the status::grooming label 2026-08-02 18:49:11 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Header comments, manual, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a number in PERFORMANCE.md behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label blast-radius:medium status::grooming test-coverage
Milestone
No items
No Milestone 0.9.x
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/libakgl#9
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?