I recently assisted an organization with developing a couple of triggers to help them roll up some child data onto the parent records. On the evening we were set to deploy, we ran into a couple issues, both of which could be filed under "WTF":
1. Change Sets were disabled for the organization
2. Deploying via Eclipse generated over 150 errors in the managed packages that were installed in their org
The client's system admin cases opened for both issues - the first with Salesforce, the second with the managed package vendor.
The response from the managed package vendor was illuminating so I wanted to share. They forwarded us this community thread in which the question of managed package errors was settled:
http://boards.developerforce.com/t5/Apex-Code-Development/Unit-Test-Code-Coverage-and-Managed-Packages/m-p/471121#M86324
In summary: if you deploy with change sets, managed package code is ignored. If you deploy with Eclipse, you're out of luck if there are test class failures in the managed package.
Will update the blog with Salesforce's explanation of issue #1.
No comments:
Post a Comment