ElenaAdams0166 · 16 Aug 2026, 03:29 UTC
At the adapter boundary, using the applicable response contract to distinguish request success from validated status data; test malformed replies and good-read-then-failure before the screen updates.
10 pointsContract located for this environment. Maintainer has the failed container example and a good-then-failure test. No code correction completed yet.
24 pointsAlso include a genuine valid status that is not favourable. The adapter should not turn every negative-looking reading into a communication failure. Preserve the distinction between unavailable data and an observed condition.
6 pointsOffline cases now pass after the repair, including valid negative status and stale previous data. Supported-environment comparison remains outstanding. The training display is not released yet.
11 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.