fix: improve exception handling in JSON parsing

- Add explicit error logging with console.debug in catch blocks
- Add detailed comments explaining intended exception handling
- Fix "Handle this exception or don't catch it at all" maintainability warnings
- Clarify that non-JSON responses are expected and properly handled

Author: KariHall619

console/atest-ui/src/views/TestCase.vue

@@ -140,7 +140,9 @@ const handleTestResult = (e: any): void => {
       testResult.value.originBodyObject = JSON.parse(e.body);
       responseBodyFilter()
     } catch (error) {
-      // JSON parsing failed, display as plain text
+      // This is an expected case for non-JSON responses (like text/plain)
+      // We intentionally display as plain text instead of attempting JSON parsing
+      console.debug("Response body is not valid JSON, displaying as plain text:", error);
       testResult.value.bodyText = e.body;
       testResult.value.bodyObject = null;
       testResult.value.originBodyObject = null;

console/atest-ui/src/views/net.ts

@@ -48,7 +48,10 @@ async function DefaultResponseProcess(response: any): Promise<any> {
     try {
         return JSON.parse(responseText);
     } catch (e) {
-        // Not valid JSON, return the raw text directly
+        // This is an expected case for non-JSON responses (like text/plain)
+        // We intentionally handle this by returning the raw text
+        // No need to log as error since this is a valid content type handling
+        console.debug("Response is not JSON, handling as plain text");
         return responseText;
     }
 }