1

While testing installation and update of a mobile application, i came up with a scenario, i.e.

i have installed application in mobile and i am already logged in to the application using valid credentials.
Now, As the flow of signup/sign-in is completely changed, when i am updating it with new version, should i stay logged-in or not in the application. what is the correct behavior?

closed as primarily opinion-based by Niels van Reijmersdal, Kate Paulk, IAmMilinPatel, Bharat Mane, NarendraC Dec 9 '16 at 5:26

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Login session should remain unharmed! – IAmMilinPatel Dec 8 '16 at 9:28
1

This something the business should decide. There are no lists of best practises.

As a tester you should not make up new requirements, you should signal that this could be an issue. Depending on effort and value the business should decide to implement it or not.

In this case as user, I would like it to stay logged in, because loggin in costs me time. But as a product owner it would depend on how easy this is to implement, couple of hours, sure, but couple of days, then maybe I would think wasting a couple of seconds of user time is acceptable.

Not the answer you're looking for? Browse other questions tagged or ask your own question.