Skip to content

Add telemetry for when user triggers testing from CLI #24562

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
Open
cwebster-99 opened this issue Dec 9, 2024 · 2 comments · May be fixed by #25103
Open

Add telemetry for when user triggers testing from CLI #24562

cwebster-99 opened this issue Dec 9, 2024 · 2 comments · May be fixed by #25103
Assignees
@eleanorjboyd @Copilot
Labels
area-testing feature-request Request for new features or functionality needs PR Ready to be worked on
Milestone
May 2025

Comments

@cwebster-99
Copy link
Member

While we have a testing UI, we know many users still run testing via the command line. Can we add telemetry to capture this behavior to get a better idea of testing usage in the extension?
@cwebster-99 cwebster-99 added area-testing feature-request Request for new features or functionality labels Dec 9, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Dec 9, 2024
@eleanorjboyd eleanorjboyd added the debt Covers everything internal: CI, testing, refactoring of the codebase, etc. label Dec 10, 2024
@eleanorjboyd
Copy link
Member

@karthiknadig what would the design for this be? Will it cause any issues to add this such as slowing down any actions?

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Feb 7, 2025
@karthiknadig
Copy link
Member

@eleanorjboyd We currently track python launches from terminal, this will be adding to that code or adding similar code to send telemetry. It does not block terminal execution, so users will not see a difference.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 10, 2025
@cwebster-99 cwebster-99 reopened this Mar 10, 2025
@karthiknadig karthiknadig added needs PR Ready to be worked on and removed info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team labels Mar 10, 2025
@karthiknadig karthiknadig added this to the March 2025 milestone Mar 10, 2025
@karthiknadig karthiknadig removed the debt Covers everything internal: CI, testing, refactoring of the codebase, etc. label Mar 10, 2025
@karthiknadig karthiknadig modified the milestones: March 2025, April 2025 Mar 25, 2025
@eleanorjboyd eleanorjboyd modified the milestones: April 2025, May 2025 Apr 28, 2025
@microsoft microsoft deleted a comment from github-actions bot May 23, 2025
@Copilot Copilot AI linked a pull request May 23, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eleanorjboyd eleanorjboyd

Copilot code review Copilot

Labels
area-testing feature-request Request for new features or functionality needs PR Ready to be worked on
Projects
None yet
Milestone
May 2025
Development

Successfully merging a pull request may close this issue.

Add telemetry for when user triggers testing from CLI microsoft/vscode-python
3 participants
@karthiknadig @eleanorjboyd @cwebster-99