cleaning up the vscode questionnaire#138
Conversation
18b1638 to
ec68e1d
Compare
| Object.entries(data.categoryBreakdown).forEach(([category, score]) => { | ||
| const scoreColor = (score as number) >= 7 ? 'green' : (score as number) >= 4 ? 'yellow' : 'red'; | ||
| console.log(` ${category}: ${chalk[scoreColor](score + '/10')}`); | ||
| const scoreColor = |
There was a problem hiding this comment.
@grrrau all of these calculations we might want to check
| // Fallback: wait additional time for CLI process to complete | ||
| await vscode.window.waitForTimeout(3000); | ||
| } | ||
|
|
| } | ||
| } | ||
| } | ||
| // // Look for the Data & Results section |
There was a problem hiding this comment.
same, all the test should exist
There was a problem hiding this comment.
@pessi-v the tests are still commented out, do you need something?
| if (!foundAnalysisTree) { | ||
| dataTree = allTrees.nth(1); | ||
| } | ||
| // // Click on Data & Results section to ensure it's expanded and active |
| // // Debug: Let's see what tree sections we have available | ||
|
|
||
| const errorMessage = `Expected to find test analysis results in Data & Results tab. | ||
| // const allTreeSections = vscode.window.locator(".pane-header"); |
| } else { | ||
| } | ||
| } | ||
| // throw new Error(errorMessage); |
| // Create .carbonara directory structure | ||
| // Note: Don't create .carbonara directory here - let each test create it | ||
| // This ensures the provider doesn't initialize with an empty database | ||
| const carbonaraDir = path.join(tempDir, ".carbonara"); |
| }); | ||
|
|
||
| test("should load and display data when assessment data exists", async function () { | ||
| test.skip("should load and display data when assessment data exists", async function () { |
| import * as fs from "fs"; | ||
| import { ToolsTreeProvider, ToolItem } from "../../tools-tree-provider"; | ||
|
|
||
| suite("ToolsTreeProvider Unit Tests", () => { |
There was a problem hiding this comment.
this file looks fine, pls double check if all tests are still there
suung
left a comment
There was a problem hiding this comment.
Looks good, but tests have been removed that should be brought back
grrrau
left a comment
There was a problem hiding this comment.
can i get a sshot please, of the state of the changes?
a272d32 to
a521977
Compare
|
Ok, I'm going to hand this over to yous now, because I won't be able to work anymore. There's some tests that need fixing, but otherwise it should be good to go.
|
@pessi-v well noted, thanks for your efforts so last minute before holiday. |
f2de23c to
60d9003
Compare
|
Dried up, added tests, made sure that the new questions are included in cli and in vscode @suung |
|
@suung can I merge this? |
I haven't looked through the code yet. |
suung
left a comment
There was a problem hiding this comment.
tests are still commented out
|
@grrrau Those changes are now in slightly different form on main, you can check the screenshots above to see if there is something you would want to port, it should be easy, namely
|

Pull Request Checklist
Legal Requirements
Code Quality
Description
Type of Change
Testing
Additional Notes