Running Apex Test from command palette is not showing in Output
See original GitHub issueIf I run a deploy command, the output window will show something like `Starting SFDX: Deploy Source to Org
15:10:21.816 sfdx force:source:deploy --sourcepath [filepath]`
If I execute an apex test command, either by clicking the Run Test link or from the command palette, the output window doesn’t show anything. Normally the output window would show the result of the command and the test coverage results, but it simply doesn’t display anything.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
sfdx plugin - VS Code: Commands run through Command ...
To see the output of the commands that you run, select View > Output, and then select Salesforce CLI from the dropdown menu....
Read more >Troubleshooting Common Issues | Salesforce for VSCode
If the Apex features aren't available, activate the Apex Language Server. In the VS Code menu bar, select View > Output and select...
Read more >Apex Test Coverage Not Displaying #1330 - GitHub
Open list of apex test classes in the sidebar and run apex test from the side, invoke apex test from the command palette,...
Read more >VS Code API | Visual Studio Code Extension API
A code lens represents a Command that should be shown along with source text, like the number of references, a way to run...
Read more >Salesforce CLI and Visual Studio Code Command Palette
The folder has been created but you need to open it in Your Visual Studio Code by clicking on Open folder shown below....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@robcowell Thanks for raising those points, we’ll log a bug to switch to the appropriate output view if you’re not already on it. This change was part of an ongoing effort to separate the roles & responsibilities of each extension - so the output for Apex test runs, anonymous Apex executions, etc. were all moved to the Apex output channel.
This is good to know, thank you for the context.