Concepts/Concept
ADPS Engineering Concept Registry
External Acceptance Probe: Let the User-Side Result Decide Success
Test the result from the user side and let that evidence decide success.
Start with a false HTTP 200
GeoServer can return a ServiceException with HTTP status 200. The publication call appears successful while the user receives an empty map. A process exit code or status code alone records a business failure as success.
Definition
An external acceptance probe performs the same action a consumer would perform from outside the system boundary. It checks status, content, and the usable result. Internal receipts remain process evidence; the probe decides whether the task commits, retries, or fails.
The Xuanxu probe issues real WMS or WMTS requests, inspects content type and exception bodies, checks that a screenshot contains non-transparent map content, and writes the result to verify_report.json.
Boundary
The probe must cover the real delivery path, not an internal shortcut. Visual checks need calibrated thresholds and known-good samples. Complex cartographic quality may still require expert sampling.
Provenance
- Initial case: Xuanxu Technology GIS publishing agent, contributed by Yuke Xiong.
- Lineage: end-to-end tests, synthetic probes, and health endpoint monitoring.
- ADPS contribution: the probe receipt directly controls the agent task state.
- Definition status: ADPS restatement.
Proposal and provenance
- Concept group
- Evaluation, reflection, and governance
- Initial source within ADPS
- Initial practice: Yuke Xiong
- First recorded in
- Xuanxu GIS publishing-agent case ()
- ADPS editorial work
- ADPS connected a user-side probe receipt to the task state machine so observable results decide success.
- Current standing
- ADPS restatement
Initial source: Xuanxu Technology GIS publishing-agent case; contributed by Yuke Xiong.
Chronicle
- Recorded source
- Xuanxu GIS publishing-agent case ()
- Source date
- First published on ADPS