Return to Answer

This is how I would debug a Selenium session to find out what is happening:

Step-by-step debugging: Most IDE's allow you todo step-by-step debugging, you could set a break point just before the point you want to investigate. This will pause the execution of the test and lets you examine the browser with its own tools. You can step thru each line of code one by one and monitor the behaviour. See this video for an example

Video recording: Record the test session with a screen-recorder or use one of the online Selenium grids like Sauce labs or TestingBot, both offer recording of the test session by default and give enough free minutes to analyse most issue's. After the recording you can playback frame by frame.

Sleeps: Like others suggest, you can add sleeps or increase the default wait-times. Personally I am not a fan of this because you might need to rerun the test a couple of times if the sleeps are not long enough.

This is how I would debug a Selenium session to find out what is happening:

Step-by-step debugging: Most IDE's allow you todo step-by-step debugging, you could set a break point just before the point you want to investigate. This will pause the execution of the test and lets you examine the browser with its own tools. You can step thru each line of code one by one and monitor the behavior. See this video for example

Video recording: Record the test session with a screen-recorder or use one of the online Selenium grids like Sauce labs or TestingBot, both offer to record of the test session by default and give enough free minutes to analyze most issues. After the recording, you can playback frame by frame.

Sleeps: Like others suggest, you can add a sleep or increase the default wait-times. Personally, I am not a fan of this because you might need to rerun the test a couple of times if the sleep is not long enough.

This is how I would debug a Selenium session to find out what is happening:

Step-by-step debugging: Most IDE's allow you todo step-by-step debugging, you could set a break point just before the point you want to investigate. This will pause the execution of the test and lets you examine the browser with its own tools. You can step thru each line of code one by one and monitor the behaviour. See this video for an example: https://www.youtube.com/watch?v=AudbOfamfwc

Video recording: Record the test session with a screen-recorder or use one of the online Selenium grids like Sauce labs or TestingBot, both offer recording of the test session by default and give enough free minutes to analyse most issue's. After the recording you can playback frame by frame.

Sleeps: Like others suggest, you can add sleeps or increase the default wait-times. Personally I am not a fan of this because you might need to rerun the test a couple of times if the sleeps are not long enough.

This is how I would debug a Selenium session to find out what is happening:

Step-by-step debugging: Most IDE's allow you todo step-by-step debugging, you could set a break point just before the point you want to investigate. This will pause the execution of the test and lets you examine the browser with its own tools. You can step thru each line of code one by one and monitor the behaviour. See this video for an example

Video recording: Record the test session with a screen-recorder or use one of the online Selenium grids like Sauce labs or TestingBot, both offer recording of the test session by default and give enough free minutes to analyse most issue's. After the recording you can playback frame by frame.

Sleeps: Like others suggest, you can add sleeps or increase the default wait-times. Personally I am not a fan of this because you might need to rerun the test a couple of times if the sleeps are not long enough.

I use two ways to investigate behaviour in the browser.

Step-by-step debugging: Most IDE's allow you todo step-by-step debugging, you could set a break point just before the point you want to investigate. This will pause the execution of the test and lets you examine the browser with its own tools. You can step thru each line of code one by one and monitor the behaviour.

Video recording: Record the test session with a screen-recorder or use one of the online Selenium grids like Sauce labs or TestingBot, both offer recording of the test session by default and give enough free minutes to analyse most issue's. After the recording you can playback frame by frame.

Sleeps: Like others suggest, you can add sleeps or increase the default wait-times. Personally I am not a fan of this because you might need to rerun the test a couple of times if the sleeps are not long enough.

This is how I would debug a Selenium session to find out what is happening:

Step-by-step debugging: Most IDE's allow you todo step-by-step debugging, you could set a break point just before the point you want to investigate. This will pause the execution of the test and lets you examine the browser with its own tools. You can step thru each line of code one by one and monitor the behaviour. See this video for an example: https://www.youtube.com/watch?v=AudbOfamfwc

Video recording: Record the test session with a screen-recorder or use one of the online Selenium grids like Sauce labs or TestingBot, both offer recording of the test session by default and give enough free minutes to analyse most issue's. After the recording you can playback frame by frame.

Sleeps: Like others suggest, you can add sleeps or increase the default wait-times. Personally I am not a fan of this because you might need to rerun the test a couple of times if the sleeps are not long enough.