Virtual User Life Cycle
Although this is a kind of newbie question, many questions in this forum related to "what happens when my vuser returns LR_FAIL", etc. are indicating that people do not understand the vuser life cycle once run within load runner controller. In all honesty, I don't understand it as well and neither this nor the Mercury forum nor the documentation give you any answers when you search for life cycle.
In my particular situation, I am looking for the life cycle model of a QTWeb virtual user, but I don't think it differs from the life cycle of any other virtual users.
I would prefer to see something like an UML state diagram as an answer but I am more than willingness to draw one by myself.
Re: Virtual User Life Cycle
Be more specific. Your definition of a life-cycle may be exactly the opposite of someone else. The fact that you cannot find it here via a search probably means something simple - the question has never been asked before. If you are referring to "a day in the life" of a user, this is documented in the Controller User's Guide, even though it is not called "a day in the life". By virtue of the fact that you plan a scenario according to the guidelines AND take into account best practices of performance testing - you might be achieving your intent.
Regarding LR_FAIL, from Vugen help:
"You can manually set the status of the transaction or you can allow LoadRunner to detect it automatically. To manually set the status, you perform a manual check within the code of your script (see example) evaluating the return code of a function. For the "succeed" return code, set the status to LR_PASS. For a "fail" return code, set the status to LR_FAIL. For an "aborted" return code, set the status to LR_STOP."
Above is Mercury copyrighted material.