cZachery wrote:Can I run tests that operate already logged in, and then log out after a sequence of tests has PASSed?
Yes, of course.
The state of being logged in or not logged in is not relevant to eValid.
Tests of an application in either case run normally.
It is the
TRANSITION from logged in to logged out and vice versa that throws everyone for a loop.
It's like a light switch. If it's on, you have to make sure that you don't turn if off. Or if it is off, you have to make sure you don't turn it on.
But
MOST -- not all, but most -- applications that have a login requirement won't behave well if you recording logging in and then fail to log out. If you do that you have left the application in a "funny sate" and the next playback of the same script won't correct it.
But you may be pleased to know that you are not alone. Recording a login and then failing to record the corresponding log out is the MOST common error in using eVald.
eValid Support
by cZachery » Fri Mar 23, 2012 3:56 pm