Add document symbol provider test

[mshr-h]

Summary

• add integration test for VerilogDocumentSymbolProvider
• run tests via runTest.ts
• correct extension path in test harness

Testing

• npm test (fails: SIGSEGV from VS Code due to missing display)

---

https://chatgpt.com/codex/tasks/task_e_6848e6ea25d88324a2f7dfe40f1f6974

[Copilot]

Pull Request Overview

This PR introduces an integration test for the VerilogDocumentSymbolProvider and updates test configurations.

• Added an integration test in documentSymbol.test.ts that verifies document symbols are returned from a simple verilog file
• Updated the test harness configuration in runTest.ts by correcting the extension development path
• Modified the test script in package.json to use runTest.js

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/test/suite/documentSymbol.test.ts	Added integration test for VerilogDocumentSymbolProvider
src/test/runTest.ts	Corrected the extension development path
package.json	Updated the test script to reference runTest.js

Comments suppressed due to low confidence (1)

package.json:595

• Ensure that the updated test runner file path matches the build output and update any relevant documentation accordingly.

"test": "node ./out/src/test/runTest.js"

[Copilot]

Consider using the workspace configuration target rather than Global in tests to minimize unintended side effects on user settings.

Suggested change

	await vscode.workspace.getConfiguration('verilog').update('ctags.path', 'ctags', vscode.ConfigurationTarget.Global);
	await vscode.workspace.getConfiguration('verilog').update('ctags.path', 'ctags', vscode.ConfigurationTarget.Workspace);