Script tests are one of the best ways to keep requests honest. They let you check that a response looks right, catches the status you expected, and protects important workflows from quiet surprises. But when a test failed, the next question was always the same: where should I look?

This update makes that answer much clearer.

When a script test fails, HarborClient now connects the result back to the exact request script that produced it. The Tests view still shows the familiar pass/fail list, expected value, actual value, and timing details, but failed rows can also take you straight to the relevant script editor.

Even better, HarborClient can now mark the failing line directly in the editor. Instead of scanning a script and guessing which check failed, you can see the failure highlighted where the expectation was written. That same visual cue appears both in the full script editor and inside the request’s PreRequest and PostRequest tabs, so you do not have to leave the workflow you are already in.

The goal is simple: less hunting, faster fixes, and a smoother feedback loop when you are building or maintaining API checks. A failed test should point you toward the next action, not send you searching through tabs.

This release also adds richer test details behind the scenes, including clearer expected and actual values, timing, and source locations when available. The result is a more helpful test report that stays close to your work and gives you better context at the moment you need it.

If you use scripts to validate responses in HarborClient, failed tests should now feel easier to read, easier to find, and easier to fix.