From 8f3d60bf378a2c50609d5512c930e4174bf61728 Mon Sep 17 00:00:00 2001
From: Eleanor Boyd <eleanorboyd@microsoft.com>
Date: Tue, 1 Aug 2023 14:32:44 -0700
Subject: [PATCH] unittest discovery errors not displaying in test explorer
 (#21726)

saw an issue where if discovery failed there was no notice in the test
explorer for unittest. It was due to a different value for the new blank
value for the payload tests. fixes
https://github.com/microsoft/vscode-python/issues/21725 and
https://github.com/microsoft/vscode-python/issues/21688
---
 src/client/testing/testController/common/resultResolver.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/client/testing/testController/common/resultResolver.ts b/src/client/testing/testController/common/resultResolver.ts
index 8baf4d0d7ae7..6e875473c836 100644
--- a/src/client/testing/testController/common/resultResolver.ts
+++ b/src/client/testing/testController/common/resultResolver.ts
@@ -68,7 +68,7 @@ export class PythonResultResolver implements ITestResultResolver {
             // remove error node only if no errors exist.
             this.testController.items.delete(`DiscoveryError:${workspacePath}`);
         }
-        if (rawTestData.tests) {
+        if (rawTestData.tests || rawTestData.tests === null) {
             // if any tests exist, they should be populated in the test tree, regardless of whether there were errors or not.
             // parse and insert test data.