Skip to content

[wasm][debugger][libs] Documentation: How to debug library tests #77368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 7 commits into from
Jan 31, 2023
Merged

[wasm][debugger][libs] Documentation: How to debug library tests #77368

merged 7 commits into from
Jan 31, 2023

Conversation

@ilonatommy
Copy link
Member

@ilonatommy ilonatommy commented Oct 24, 2022 •
edited
Loading

Basic scenario of how to debug library tests in Chrome DevTools and VS Code.
Partial solution for issue: #76721.

@ilonatommy ilonatommy added documentation Documentation bug or enhancement, does not impact product or test code arch-wasm WebAssembly architecture area-Debugger-mono labels Oct 24, 2022
@ilonatommy ilonatommy self-assigned this Oct 24, 2022
@ghost
Copy link

ghost commented Oct 24, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Pinning a PR, so that it won't get lost. The draft will get changed once we solve problems listed here #76721 and will be able to include screenshots and verify errors in the description.

Author: ilonatommy
Assignees: ilonatommy
Labels:

documentation, arch-wasm, area-Debugger-mono
Milestone: -

@ilonatommy ilonatommy mentioned this pull request Oct 25, 2022
Open
8 tasks
@ilonatommy ilonatommy requested a review from thaystg November 15, 2022 10:04
@ilonatommy ilonatommy changed the title [wasm][debugger][documenatation] Debugging library tests [wasm][debugger][libs] Documentation: How to debug library tests Nov 15, 2022
@ilonatommy ilonatommy marked this pull request as ready for review November 15, 2022 10:08
@radical
Copy link
Member

radical commented Nov 15, 2022

Do these steps work with codespaces too?

@ilonatommy
Copy link
Member Author

ilonatommy commented Nov 22, 2022 •
edited
Loading

Do these steps work with codespaces too?

  • Codespaces in browser: no. Reason - remote debugging cannot be opened there:
    ERROR: We can't launch a browser in debug mode from here. Open this workspace in VS Code on your desktop to enable debugging.

  • Codespaces in VS Code Desktop: I cannot find a proper way to launch chrome from VS Code Desktop. It might be working but I have problems with checking it.

@radical
Copy link
Member

radical commented Nov 22, 2022

Do these steps work with codespaces too?

  • Codespaces in browser: no. Reason - remote debugging cannot be opened there:

ERROR: We can't launch a browser in debug mode from here. Open this workspace in VS Code on your desktop to enable debugging.

  • Codespaces in VS Code Desktop: I cannot find a proper way to launch chrome from VS Code Desktop. It might be working but I have problems with checking it.

I can walk you through for that.

@pavelsavara
Copy link
Member

pavelsavara commented Jan 6, 2023

since the guide is wasm specific, should we rename the file ?

@ilonatommy ilonatommy mentioned this pull request Jan 31, 2023
Merged
@ilonatommy ilonatommy merged commit f8ab555 into dotnet:main Jan 31, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Mar 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@thaystg thaystg thaystg approved these changes

Assignees

@ilonatommy ilonatommy

Labels

arch-wasm WebAssembly architecture area-Debugger-mono documentation Documentation bug or enhancement, does not impact product or test code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@ilonatommy @radical @pavelsavara @thaystg