The current product I'm testing requires users to connect their financial information (such as their bank, credit cards, etc.); after this info is connected, the user is shown their balances, credit lines, etc. What should I keep in mind, given that not all users will be comfortable inputting/having this info displayed in front of a researcher/recorded?
Could I provide users with "fake" log-in credentials they can use? The pitfall with that is I'm also testing how many accounts the user would connect until they feel satisfied. I don't want to pre-determine how many accounts a user is likely to input; rather I'd like to get a sense of how many they feel is enough for our database to get an accurate understanding of their financial status.
I think this also speaks largely to the question of how to conduct usability testing with sensitive/private info.