Choosing Thread > Step Over in a debugger "steps over" the next function call that occurs in that debugger's thread, executing the call in full and then returning control to the debugger. The command operates in the context of the currently selected call frame in the debugger's stack pane.
Consider this stack backtrace
[-] Thread 1: "Master thread"[+] concerto [+] opus
The selected frame is concerto, the source code for which looks like this:
define method concerto () => ()
first-movement(#"moderato");
second-movement(#"adagio-sostenuto");
third-movement(#"allegro-scherzando");
end method;
Where execution was paused in the call to second-movement. Choosing Thread > Step Over runs through the entire execution of second-movement before returning control to the debugger.
Thread > Step Over does an implied Thread > Step Out too, so that if when you choose Thread > Step Over there is no more code, it steps out rather than continuing the application no longer under the debugger. See Section 6.12.3 for details of Thread > Step Out.