I provide a standardized but unmanaged package to clients who have different workflow needs. The workflows sometimes interfere when I deploy new standard code. Does it make sense to turn them off? That would mean that after deployment when I turn them back on again, the tests would fail.
Example: My clients use validation rules that accept only certain amounts for membership dues. They all have different amounts. On top of it they sometimes change the amounts. When I test code for the online payments module, I insert opportunities with random amounts, but if those amounts aren't the same as the ones the client instance accepts, the test fails. I could modify the test amounts to fit the current validation rule, but later the organization could change the accepted amounts and the test would fail again.
Any guidance on this? Thanks, Baird