I have my first InfoPath form coming up for testing. This uses a GetCommonMemberships data connection as a condition for various rules (for example, form load rules
that switch views when the user is a member of a Packaging AD group). I’m not a member of any of the AD groups being used for these conditions and neither are the company’s QAs.
Because I’m not a member of any of the groups, I tend to set my rule up in reverse to check it. For example, if I have a rule where the DisplayName is equal
to “domain\Packaging” (of which I am not a member), the control is not disabled for me. This assumes that the opposite is also true if I change the rule to is not equal to “domain\Packaging”. In other words, the control should not be
disabled for members of that group but it should be for me.
How do you guys allow your QAs to impersonate different team members to properly test this without compromising the integrity of the form?
View Complete Post