Package installation fails if subscriber's org has a validation rule that is fired as part of tests executed during package installation
Last updated 2016-07-28 ·Reference W-2620102 ·Reported By 2 users
In Summer '15, the new package installer may prevent package installations if the subscriber's org has a validation rule that meets this criteria:
a) It refers to a custom field, and
b) It is evaluated as part of a DML operation performed by a test method executed during package installation.
a) In a Summer '15 test org, create a custom text field on User called Test__c.
b) Create a validation rule on Accounts using the following error formula:
Notice this will evaluate to false unless you enter a value on this field in your user record. As a result, you should be able to create an account successfully.
c) Try to install a package that contains a test that runs during package installation and that performs a DML operation on Accounts. This will fail with this exception:
System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Validation Formula "<validation_rule_name>" Invalid (Test__c does not exist. Check spelling.): 
Append &newUI=0 to the installation URL to use the old package installation link. E.g.
NOTE: This query string parameter should only be used as a workaround to this bug while it is addressed.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.