italia/developers-italia-api

Webhooks and catalogs lack DB persistence checks for write endpoints

Open

#384 opened on May 10, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (8 forks)auto 404
good first issue

Repository metrics

Stars
 (16 stars)
PR merge metrics
 (PR metrics pending)

Description

Most resources have endpoint tests that only verify the HTTP response, not what actually lands in the database. POST and PATCH can return 200 with the right body and still write the wrong row, and DELETE can return 204 without removing anything.

logs, publishers and software already have TestXxxPostDBChecks, TestXxxPatchDBChecks and TestXxxDeleteDBChecks (in #294 and follow-ups). Two resources are still missing equivalent coverage:

  • webhooks: no DB persistence checks for POST, PATCH or DELETE
  • catalogs: existing checks cover only catalog_sources and DELETE, nothing asserts that POST or PATCH actually persist name, alternativeId or publishersNamespace on the catalog row itself

Contributor guide

Research direction
Examine existing `TestXxxPostDBChecks`, `TestXxxPatchDBChecks`, and `TestXxxDeleteDBChecks` for logs, publishers, and software (from issues #294 and follow ups). Replicate their structure for the webhooks and catalogs resources.
Tech stack
go
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Gotesting basicsdatabase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75