Jason Driscoll - 5 years ago
Yet another frustration. Run test (in Console), shows % covered & lines covered/total lines. Open the code coverage result and lines covered are highlighted as well as lines not covered. Cool.
Now modify class getting tested by removing a couple of methods that are no longer needed....and re-run test.
Hmmm, total lines didn't change, shoud have gone down. Open the code coverage result and highlighting is off. It's highlighting lines that shouldn't be highlighted and vice versa.
Anybody know how to reset this to show updated class and code information?
Jeff May - 6 years ago
@Benjamin Pirih -- great points. That is exactly the reason I wrote the Admin Test Runner AppExchange package!!! It gives Admins a way to know how their tests are doing and warns them when there are problems: https://appexchange.salesforce.com/listingDetail?listingId=a0N3000000B52wnEAB
Benjamin Pirih - 6 years ago
What upsets me most about this change is it hides code coverages from Administrators placing the 75% minimum code coverage responsibility on the developers shoulders.
Administrators are no-longer aware of lowering code coverage standards. Often developers aren't aware that an Org is failing the 75% until attempting deployments.
Unit tests should be run automatically daily by the system. Test results and overall code coverage should be an indicator of system health. This indicator should be available to a System Administrator without having to enter a "Developer Console".
System health / Code coverage is not solely a Developer responsibility!
Administrators need to be aware of code coverage and the fact that Org changes can break / drop code coverage..
Lucas Cushanick - 6 years ago
I do like the Developer Console and find it an invaluable addition to my development, particularly for quick fixes. I also use MavensMate and the Eclipse IDE for elaborate projects; you use the right tool for each job. What makes this idea valuble to me is the research and identify Apex Class coverage that is low. I have not yet been able to sort on that column in the Dev Console and scrolling through hundreds of Classes looking for < 75% is inefficient. The test panel as it exists now needs to be improved.
Paul Narsavage - 6 years ago
Josh's comment from Production Management is quite disheartening and frustrating... Granted, no one likes change, but the outcry of fellow developers here clearly shows that this isn't just about change. It's about the fact that the Developer Console is a bloated, complex, over-hyped, slow, non-intuitive, unreliable, immature "tool". It frequently crashes and cannot load the large logs and classes that we have in our organization. The custom/complex interface makes it hard to get lists of classes and code coverage (used to be able to copy/paste from standard HTML pages).
Euan Greig - 6 years ago
The developer console in its present form is simply not fit for purpose. As others have said, it is buggy and slow. Also very poorly designed, in particular but not just in the way that code coverage is shown. It causes me immense amounts of frustration and swallows up time that I could be using doing my real job of developing instead of fighting this tool. Please give us back the simple and intuitive tools we had before. And please please please do not migrate any more functionality to the consoie.
If you won't do this out of consideration for developers, consider your own interests. My company is already developing less on Salesforce because of the frustrations involved in working on this platform, and I shouldn't think we are the only ones.
Rachel Cole - 6 years ago
The Developer Console is extremely buggy, and it's very difficult to try to depend on it for viewing code coverage. Code coverage often randomly fails to display, or it will only display for each individual test, not showing what all of the tests (in the same test class!) cover in one class.
Contacting support about this issue has been less than helpful, and usually entails removing all test coverage and re-running, which can take upwards of 12 hours to re-run everything.
I'm on board for having one tool that's supported, but it needs to be a tool that actually works, not something that is clealry poorly thought out and implemented.
Agio Technology - 6 years ago
Developer console currently requires modify-all permissions. While I have a developer profile, I do not have modify-all permissions in my production org.
This means, that while I can deploy code, I no longer have an independent means to resolve code coverage issues.
This is a horrible user experience, and from what I see, the removel from the classes list view is not a desired move by the developer community. SF is supposed to be assisting with rapid development process, how is this change helping us to be faster?
We need export options, and sorting by percentages, and durations so we can target problematic areas.
Reporting capabailities on code coverage would be a plus as well.
Throw us a bone here, SF.. don't take it away from us.
Frank Wolfe - 6 years ago
We are about to go live and with almost 500 classes and ove 100 triggers, I have no way to get a holistic view of test class coverage. It appears that I will have to transcribe the code coverage from the Developer Console. This will take a huge amount of time and have to be manually maintained. Not a good way to ensure customer success.