test: terminal quick fix telemetry

[meganrogge]

Refs #167473

• Windows @bamurtaugh
• macOS @weinand
• Linux @rzhao271

Complexity: 3

Authors: @meganrogge @Tyriar

Create Issue

---

Turn on log level: trace and verify that the info for terminal/quick-fix is correct for all of the types of quick fixes we offer:

• git similar : git sttatus
• git push : checkout a branch that has no upstream and git push
• git create PR : git push --set-upstream origin <branch-name>
• git two dashes: git add . -all
• free port : launch a server or task that uses a specific <port> then launch that again so you see an error related to address already in use

[weinand]

@meganrogge I don't understand what to do here.

[bamurtaugh]

I'm also not sure what to do here - additional info / examples would be super helpful!

[Tyriar]

Sorry about that. Open up the telemetry log channel as described in https://code.visualstudio.com/docs/getstarted/telemetry#_output-channel-for-telemetry-events, then trigger quick fixes as described in https://code.visualstudio.com/docs/terminal/shell-integration#_quick-fixes. Validate you see events for each of the quick fixes.

[weinand]

@Tyriar thanks, that was helpful.

[rzhao271]

Also, what are some steps I can try to get the free port message to show up?
I don't remember the last time I encountered that scenario.

[Tyriar]

@rzhao271 this is my typical test:

1. Clone https://github.com/xtermjs/xterm.js
2. Run yarn
3. ctrl+shift+b to run default build task (first server)
4. Open a new terminal and run npm start (conflicting server)