Our dashboard for diagnostic status retrieval on Fairino FR10 expected a status value from the old SDK.
The replacement environment returns a container with extra information, and our screen now shows a plausible status even when a request fails.
This is in a bench integration setup, with a fixture block as a reference.
I'm trying to fix how we interpret the answer.
Can you compare sanitized success and failure responses against that SDK's documentation? The useful detail is which field your wrapper treats as status.
@HazelChan1093 I've checked our saved examples. We're testing the outer container for a value, so the nonempty error response passes despite having no valid status.
Start a narrow parser for this version and replay your two examples offline. Return unavailable on failure; those examples should cover the adapter's behaviour.
Fair point. Those two are a regression case, not full coverage. The adapter also needs documented error cases, transport exceptions and malformed responses exercised.