Optional Steps in QTP/UFT
While automating with UFT, we face scenarios where a step is not necessarily required to complete a run session successfully.
Consider a scenario where you add login steps to your code because the application you are testing prompts to enter a username and password in a login window. Consider also that this application remembers user login details so that you do not need to login every time you open the application.
During a run session, the application does not prompt you to enter your user name and password because it retained the information previously entered. In this case, the steps that you added for entering the login information are not required. We should mark these steps optional.