Attempt to diagnose issue by removing new test command calls

Author: vezwork

apps/vscode/src/test/quartoDoc.test.ts

@@ -25,18 +25,17 @@ suite("Quarto basics", () => {
     const doc = await vscode.workspace.openTextDocument(exampleWorkspaceOutPath("hello.qmd"));
     const editor = await vscode.window.showTextDocument(doc);
 
-    console.log('extension().isActive', extension().isActive);
-
     await extension().activate();
+    await wait(APPROX_TIME_TO_OPEN_VISUAL_EDITOR);
 
     // manually confirm visual mode so dialogue pop-up doesn't show because dialogues cause test errors
     // and switch to visual editor
-    await vscode.commands.executeCommand("quarto.test_setkVisualModeConfirmedTrue");
+    // await vscode.commands.executeCommand("quarto.test_setkVisualModeConfirmedTrue");
     await wait(300); // It seems necessary to wait around 300ms for this command to be done.
     await vscode.commands.executeCommand("quarto.editInVisualMode");
     await wait(APPROX_TIME_TO_OPEN_VISUAL_EDITOR);
 
-    assert.ok(await vscode.commands.executeCommand("quarto.test_isInVisualEditor"));
+    // assert.ok(await vscode.commands.executeCommand("quarto.test_isInVisualEditor"));
   });
   // Note: this test runs after the previous test, so `hello.qmd` has already been touched by the previous
   //       test. That's okay for this test, but could cause issues if you expect a qmd to look how it
@@ -50,7 +49,7 @@ suite("Quarto basics", () => {
     const docTextBefore = doc.getText();
 
     // switch to visual editor and back
-    await vscode.commands.executeCommand("quarto.test_setkVisualModeConfirmedTrue");
+    // await vscode.commands.executeCommand("quarto.test_setkVisualModeConfirmedTrue");
     await wait(300);
     await vscode.commands.executeCommand("quarto.editInVisualMode");
     await wait(APPROX_TIME_TO_OPEN_VISUAL_EDITOR);