[WIP] Debug tests

[cte]

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist:

• My code follows the patterns of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

Additional context

Related Issues

Reviewers

---

Important

Debug tests by modifying GitHub Actions, Jest configurations, and adding logging for debugging purposes.

• GitHub Actions:
  • Modify code-qa.yml to run jest tests with --runInBand for test-extension and test-webview jobs.
  • Add lhotari/action-upterm@v1 to test-extension job for debugging.
• Jest Configurations:
  • Comment out jest-simple-dot-reporter in jest.config.js and webview-ui/jest.config.cjs.
• Tests:
  • Add console logs in applyGitFallback() in edit-strategies.ts for debugging.
  • Skip test "should return original content with 0 confidence when changes cannot be applied" in edit-strategies.test.ts.
  • Add console.log statements in LocalCheckpointService.test.ts for performance measurement and debugging.

^{This description was created by for c1f93dd. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: c1f93dd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

The 'randomize: true' option is not a standard Jest configuration property. Please verify if this is supported by a custom test sequencer or intended—otherwise consider removing it.

Suggested change

randomize: true,

[ellipsis-dev]

Consider pinning the version of the upterm action to a specific commit hash instead of using a floating tag ('v1'). This helps ensure stability and minimizes security risks.