All Ideas

Idea Details

Post an Idea
6,940  Points
Not Planned
No plans to implement idea.

Put back Code Coverage column to Apex Classes and Apex Triggers page

Apex

Winter 14 release removed Code Coverage column from Apex Classes and Apex Triggers page.
Developers forced to check their code coverage thru Developer Console, and click each class to view the code coverage lines.

We need a page to view all classes/ triggers code coverage in a glance, not go in individual class / trigger to check the code coverage.

Please put back code coverage column back to Apex Classes and Apex Triggers page

Merge Idea · Flag

Latest Comment from Salesforce

  • Josh Kaplan - 3 years ago

    Code coverage can be queried using SOQL. You can use the query editor in developer console to view the results, and sort them. What's more, you can sort by number of uncovered lines, which is more relevant than percentage.

    Select ApexClassOrTriggerId, NumLinesCovered, NumLinesUncovered from ApexCodeCoverageAggregate
    (select the "Use Tooling API" box in the query editor tab)

    Community-supported tools like Robert/JD's are excellent. If you find them useful, please use them and help improve them.

    Moving forward, the Developer Console will be the supported tool for browser-based development on the platform.  It is costly to support multiple tools that perform the same function, so we are migrating everything to a single application.
  • Upvotes
  • Downvotes

Ideas

Apps

from AppExchange

Questions

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



 

 

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


 

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.