简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
NaomiBarnes0593 · 2025年12月24日 04:09 UTC
Restrict the substitute to that documented method and its arguments, using the interface version your application targets; what response does the parser actually expect beyond a successful call?
23分A status result with fields our parser reads. True has been skipping that path in the test wrapper. So it was not testing the parser at all.
12分Test the parser with representative version-linked responses, including failures and malformed content, and check the displayed result; rejecting the misspelled method is a useful first check but leaves that skipped path unanswered
12分Our software check once compared only whether a window opened. Could you deliberately damage one expected field and show that the test fails for the intended reason? I would find that easier to trust than another green summary.
9分Did the revised test exercise the parser, Naomi, including the first request failing before any valid status exists? An old successful value can hide that case.
19分Yes. Wrong method and malformed fields now fail explicitly; an initial failed read displays unavailable. The old substitute is removed from these tests. Comparison with the installed interface is still outstanding.
6分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .