question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Switch to Apex output channel automatically after running Apex tests

See original GitHub issue

Summary

After running Apex tests from the sidebar, command palette, or code action, the output should automatically be displayed via the Apex output channel. Currently to display the output, the user needs to manually select the Apex output channel from the drop down list provided. VS Code should automatically switch to the appropriate output channel as needed.

Steps To Reproduce:

Select a test to run via the sidebar Run test Look for results in output window at the bottom of the screen

Expected result

When the command finishes running, user should immediately see the results in the output window below - regardless of what channel the window was originally on.

Actual result Nothing happens.

VS Code Version: 50.17.0 and up

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
robcowellcommented, Mar 2, 2021

I think this may be a broader change than just Apex tests - example scenario :-

  • Ran tests, now watching in the Apex view
  • Tests fail, requiring code change
  • Edit code, save it - push on save enabled in VS Code
  • Expected : switch to Salesforce CLI view automatically so I can see confirmation of save/compile cycle to Org
    
  • Actual : it stayed on the Apex tab
    

So while I understand the “separation of concerns” for the plugin pack, following context and moving to appropriate views would greatly support this change

0reactions
AnanyaJhacommented, Mar 11, 2021

Displaying the Apex output channel automatically was addressed by release v51.4.0, closing this issue now. Feel free to open a new issue if there are any other inconsistencies.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Get Daily Limit for Running Apex Test Classes Asynchronously
Use the new DailyAsyncApexTests limit information in the Limits REST resource to understand your org's limit for asynchronous Apex test executions. The Da....
Read more >
VS Code extension no longer including line number in Apex ...
When I run Apex tests from VS Code (leveraging Salesforce CLI), I'm accustomed to the output telling me what line my tests failed...
Read more >
Build Tests Automatically with Flow Test Builder - UnofficialSF
Autolaunched Flows can be launched via a REST or Apex call. That means that you can create tests that invoke the flows, passing...
Read more >
Regression "SFDX: Deploy source to org" automatically runs ...
Summary Using the "SFDX: Deploy source to org" command from the VS extension, and targeting a production environment, it now automatically run the...
Read more >
Gearset suggested Apex tests
When deploying or validating a package to Salesforce using Gearset, you're able to specify which Apex test classes you want Salesforce to execute...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found