4 ms·
There's a multitude of reasons why review teams do not wish to create an account to test your app. Repeat testing is an obvious one, for clutter avoidance (and
by inopinatus 5y ago
There's a multitude of reasons why review teams do not wish to create an account to test your app. Repeat testing is an obvious one, for clutter avoidance (and close relation, namespace pollution issues), email failures, payment barriers, variations between plans and account types, inadvertent secrets reuse, staff unauthorized to accept any additional T&Cs, simple efficiency, the list goes on.
- deleted 5y ago[deleted]
- zelphirkalt 5y agoA prepared account for them is no good either. It could be a special account, makes the app work differently and all their review is for a manipulated test scenario.
- inopinatus 5y agoAllowing the assumption of malice to overwhelm all other concerns is rarely a wise process. There are other equally easy ways to trigger alternative behaviour. This is why review teams invest in static analysis tooling.