Like I said. You don't need a password just because you use a login form and I never said you did. In fact, I said you didn't. If you use one, they get to pick it so they'll remember it. It is simply better security.
The funny thing is, sometimes, I do it your way too.
My choice also depends on the client requirements and environments, but rarely for my convenience.
Testing is important enough that you do it properly. Changing security settings on the fly can never be a valid method. Think about it. You build the security in your test environment to begin with. Then to test it you have to change it? Not a good plan. What if you forget and don't fix it before moving to production.
I can use more than one test plan, right? Like, one for each group or scenario? It's not that hard to add a step in the test plan to modify my membership, is it? Also, do you really consider moving a user from one security group as actually changing a security settings? If I add a new user to the system, am I changing security settings then?
I did. A Loooooooooooong time ago. At least three times.
No problem. Apologies to the OP.Time out guys, please?
This dialogue has been going on since post #18, and the dialogue has just been between the two of you. We are now at #45.
Can we please just agree to disagree?
