Louisa Vanderkruk - 5 years ago
The debugging does appear in the logs, as one big log, which is truncated for large deployments. Would be good for it to either not be truncated or broken up into smaller segments. |
Joel Rankin - 6 years ago
I too am struggling with a change set in production that works perfectly in our sandbox environment but my own defined test cases fail when validating the deployment in production. I have plenty of logging in my Apex code which would help get to the bottom of the problem. Unfortunately it doesn't look like there's a way to get to this debug information from a deployment. If anyone has suggested workarounds I'd love to hear them. |
Brenda Finn - 6 years ago
This would be immensely valuable and reduce the long cycle of validating and trying to add more and more assertions to understand why there is an issue. especially in an org where there are a lot of unit tests that need to get executed. |
Dmitry Nikolaev - 6 years ago
I am really confused with a test that works in both sandbox and production, but fails during deployment. And even more confused with an impossibility to get debug logs... |
Kevin McAuliffe - 6 years ago
This would be really helpful. As is, I'm stuck with using a series of assertions to isolate the issue when I need to debug something in production that does not show up in test. |
Joanne Hicks - 6 years ago
Ditto all the above. Would add that having control over the Debug Log output would be great and better than an all or nothing approach. |
Cathy Halper - 6 years ago
agreed... I have 3 test methods that are fine in Sandbox but fail when i move to production... very confused and i believe logs would help tremendously. Thanks. |
Pedro Jauregui - 8 years ago
This will be really helpfull when the test methods fails in PRD but not in Sandbox. With this log will be much easier to know whats happening. |
EHSAN MAHMOUDI - 5 years ago