Timeline for Code coverage error when deploying to another sandbox, but Salesforce doesn't show which classes are missing coverage
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 30, 2018 at 13:31 | vote | accept | Renato Oliveira | ||
| Oct 30, 2018 at 13:20 | answer | added | Lieven Juwet | timeline score: 11 | |
| Sep 19, 2018 at 10:14 | comment | added | Renato Oliveira | No. But I did manage to deploy what I needed, by creating a package first without apex metadata and then another package just with my classes. A single package with all of them were giving this error on deployment. | |
| Sep 19, 2018 at 3:16 | comment | added | Ronnie | Did you get this figured out? | |
| Sep 14, 2018 at 2:03 | answer | added | Ronnie | timeline score: 0 | |
| Sep 13, 2018 at 21:36 | comment | added | kurunve | I am sorry, haven't seen that. As an option, I can suggest you to retrieve changeset content using ant or workbench (linkedin.com/pulse/…) from source org and deploy to target -- probably that will give more information | |
| Sep 13, 2018 at 21:28 | comment | added | Renato Oliveira | Can't change the language to English. It is a single language org. | |
| Sep 13, 2018 at 21:28 | comment | added | kurunve | I suggest you switch language to english -- sometimes salesforce errors are not consistent in case of non-english language | |
| Sep 13, 2018 at 20:39 | history | edited | Renato Oliveira | CC BY-SA 4.0 |
Added screenshot.
|
| Sep 13, 2018 at 20:37 | comment | added | Renato Oliveira | No triggers in the package. I'll upload a screenshot in a moment. There is one trigger involved in the contents, which is related to the Case object. But I'm using a trigger handler framework (I have one line on the trigger which calls a class to handle the different contexts, so if there's coverage issue on the trigger, this class should be showing). | |
| Sep 13, 2018 at 20:35 | comment | added | Bob Lopez | Can you share a screenshot? My guess is that you either have Apex Trigger(s) without any coverage (although, you typically will see which ones have 0% coverage) or your Total Org Coverage is below 75% | |
| Sep 13, 2018 at 20:00 | history | asked | Renato Oliveira | CC BY-SA 4.0 |