Skip to content

Refactor cli calling to be the same way everywhere#74

Open
suung wants to merge 6 commits into
mainfrom
66_refactor_cli_calls
Open

Refactor cli calling to be the same way everywhere#74
suung wants to merge 6 commits into
mainfrom
66_refactor_cli_calls

Conversation

@suung
Copy link
Copy Markdown
Collaborator

@suung suung commented Oct 10, 2025

  • Refactor cli calling to be the same way everywhere
  • Fix bug in json mode
  • Add better seperation of workspace fixtures with and without data and use them across all tests
  • Remove test that tests arbitrary performance
  • Add build scripts for package management

- Fix bug in json mode
- Add better seperation of workspace fixtures with and without data and use them across all tests
- Remove test that tests arbitrary performance
- Add build scripts for package management
@suung suung requested a review from pessi-v October 10, 2025 21:00
@@ -278,6 +278,114 @@ test.describe('Carbonara VSCode Extension E2E Tests', () => {
}
});

test('Scenario 1: Load workspace with existing data - data should appear', async () => {
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I separated the test scenarios for existing data to be shown, no data and, no data but after tool calling there should be data

#!/usr/bin/env node

// Script to add test-analyzer data to the with-carbonara-project fixture
const sqlite3 = require('sqlite3').verbose();
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would need to change to sql.js

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@suung

// Check that project was created in database
const initSqlJs = require('sql.js');
const SQL = await initSqlJs();
const dbData = fs.readFileSync(dbPath);
const db = new SQL.Database(dbData);

@suung suung changed the title Refactor cli calling a bit to be the same way everywhere Refactor cli calling to be the same way everywhere Oct 13, 2025
Comment thread plugins/vscode/.vscodeignore Outdated

# Build artifacts
out/
# out/ - commented out because this contains the compiled extension
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The build folder is now dist/ and as such unified with the rest of the carbonara project

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pessi-v thanks, so how should (or does) this file look like?

suung added 3 commits October 13, 2025 14:25
- Keep CLI integration as active implementation
- Preserve core integration code as comments for future use
- Update test structure to match main branch organization
- Fix CI test skipping to run unit/integration tests
- Add packaging scripts for versioned builds
- Update fixture paths to new test structure
- Add headless mode arguments for CI environments
- Prevents X server errors in Linux CI environments
- Tests now run successfully in CI without display server
- Add comprehensive headless arguments for CI environments
- Include --headless, --disable-web-security, and other display-related flags
- Should resolve Missing X server or DISPLAY errors in CI
@suung suung mentioned this pull request Oct 13, 2025
suung added 2 commits October 13, 2025 16:05
- Remove --disable-dev-shm-usage which may cause issues
- Keep only --no-sandbox and --disable-gpu for CI
- These are the most reliable arguments for VSCode extension testing in CI
- Revert runTest.ts to original state without headless arguments
- Update test:ci-check to skip VSCode extension tests entirely in CI
- VSCode extension tests require a display server which is not available in CI
- This allows CI to pass while keeping local testing functional
Copy link
Copy Markdown
Collaborator

@pessi-v pessi-v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests should be using sql.js, but otherwise fine

@suung
Copy link
Copy Markdown
Collaborator Author

suung commented Oct 20, 2025

The tests should be using sql.js, but otherwise fine

can you point me to that @pessi-v how it should be?

@pessi-v
Copy link
Copy Markdown
Collaborator

pessi-v commented Oct 29, 2025

The tests should be using sql.js, but otherwise fine

can you point me to that @pessi-v how it should be?

@suung

// Check that project was created in database
const initSqlJs = require('sql.js');
const SQL = await initSqlJs();
const dbData = fs.readFileSync(dbPath);
const db = new SQL.Database(dbData);

@grrrau
Copy link
Copy Markdown
Collaborator

grrrau commented Oct 30, 2025

@suung @pessi-v what's blocking this?

@suung suung added this to the December milestone Nov 27, 2025
@suung suung added the clarify label Dec 9, 2025
@suung
Copy link
Copy Markdown
Collaborator Author

suung commented Dec 9, 2025

@grrrau I am not sure anymore about this one, It's in december release which seems fine, I would suggest we discuss it after a round of testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants