TestNG: Parallel Execution: Handling Multiple browser and switching to new Window

Question

I do have a Test Suite with actually 20 Test Cases defined in 20 separate classes which needs to be Executed in parallel in browser Firefox on Linux OS
1. Some TC's have Java code which handles/opens new windows which passes control to these windows based on title of new window opened
2. When executed serially all TC's passes.

When trying to execute parallely through Xml file with thread count=3, and timeOut=10 sec(10000 mili sec) maximum for each TC's

My Question: How will the webDriver Handles this situation(If Multiple windows are opened)???? and wont there be a conflict and how will the webDriver transfer the control to Exact windows before the window closes and pass the TC's???? Needs to execute/pass all the 20 Tc's within the maximum time frame.

P.S: Needs some valuable Suggestions to address this issue.

Satish Gupta · Accepted Answer · 2016-08-10 16:59:44Z

1

Webdriver has nothing to do with parallelization, It is TestNG feature. Basically we execute testng tests in parallel which spawns their own browsers or driver instances, these instances are totally independent of each other and are uniquely identified by sessionid. Now even if some of these browser open in new tab or window they are tightly coupled because sessionid remains the same. I can confirm this because i have maintained such a setup and with no problem.

answered Aug 10, 2016 at 16:59

Satish Gupta

1,4671 gold badge12 silver badges14 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Ag_Yoge Over a year ago

satish thanks for the info. But when tried to execute all the TC's which gets passed when executed normally are returning Null pointer exception when tried to execute parallely.. The TC's are executed but NULL is being returned even though return Driver.getTitle(); method is being used adn all the TC's are failing.. Any suggestions on hoe to handle this Error Please?

Satish Gupta Over a year ago

Yes i think i should be able to help. Could u please provide stacktrace of null pointer. Is it during driver creation?

Ag_Yoge Over a year ago

thanks for the help and i was able to understand the root cause of the problem as all the windows are tightly coupled with session ids. Passing sessionid to already expired browser windows seems to be too complicated ways so trying to find other alternate solutions.

Collectives™ on Stack Overflow

TestNG: Parallel Execution: Handling Multiple browser and switching to new Window

1 Answer 1

3 Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Related