No, you heard it wrong. step over and step into are used while debugging.
Excerpt from QTP help-
Step Into runs only the current step in the active test or function library. If the current step calls another action or a function, the called action or function is displayed in the QuickTest window, and the test or function library pauses at the first line of the called action or function.
Step Over runs only the current step in the active test or function library. If the current step calls another action or a user-defined function, the called action or function is executed in its entirety, but the called action or function script is not displayed in the QuickTest window. The run session then returns to the calling test or function library and pauses at the next line.
refer QTP help for more details on debugging.
Excerpt from QTP help-
Step Into runs only the current step in the active test or function library. If the current step calls another action or a function, the called action or function is displayed in the QuickTest window, and the test or function library pauses at the first line of the called action or function.
Step Over runs only the current step in the active test or function library. If the current step calls another action or a user-defined function, the called action or function is executed in its entirety, but the called action or function script is not displayed in the QuickTest window. The run session then returns to the calling test or function library and pauses at the next line.
refer QTP help for more details on debugging.