KEMBAR78
Integration test status · Issue #44 · microsoft/vscode-js-debug · GitHub
Skip to content

Integration test status #44

@roblourens

Description

@roblourens

The current status of failing Chrome integration tests ported from the old codebase

Had to run some of these individually to get a clean run, since Chrome doesn't always shut down.

  • "Attach without specifying a url"
    • Attach request
  • 2 adapter.test.ts case sensitivity tests
    • Need to patch dc.launchRequest same as dc.launch
  • "should stop on debugger statement"
    • "debugger" pause reason
  • "Unknown request should produce error"
    • Timeout, looks for certain error response
  • "Hit breakpoint on JavaScript when source map is invalid"
    • Crashes adapter, exception thrown from source-map
  • 2 "Should launch successfully on port 0" tests
    • Not hooked up properly (?)
  • "Unusual source-maps"
    • Column off by 1
  • "Should stop on a breakpoint in an in-line script"
    • Stack frame format (?)
  • "No unhandled exceptions when we parse invalid JavaScript code"
    • Looks for certain error output
  • 3 "loaded sources" tests
    • "debugger" pause reason
    • And late "continue" events (DA sends "continue" after disconnect which Pinezorro will not like)
  • 4 "stack traces" tests
    • Some difference in formatting
  • Some others previously disabled as failing
  • Many hit condition breakpoints
    • Not implemented
  • Break on load related tests
    • Needs investigation
  • React framework tests
    • Needs investigation

Also only Chrome tests have been ported. There are a smaller number of node tests that I need to port as well.

Metadata

Metadata

Assignees

Labels

debtCode quality issues

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions