Display results as :

Rechercher Advanced Search

Latest topics
» Regarding Alert Interface
Fri Feb 24, 2017 2:00 pm by karthikeyakumar

» Geting issues in identifying the elsements in webdriver
Fri Feb 17, 2017 4:41 pm by janbaskt

» WebDriver - why not to use a singlton for it?
Fri Feb 17, 2017 4:40 pm by janbaskt

» WebDriver session when using testng annotation to invoke driver instance
Fri Feb 17, 2017 4:39 pm by janbaskt

» Selenium fails to launch Chrome
Fri Feb 17, 2017 4:39 pm by janbaskt

» why do i get this error
Fri Feb 17, 2017 4:38 pm by janbaskt

» Selenium Tutorial
Thu Feb 16, 2017 5:21 pm by Rahul

» When to use Selenium IDE, RC and WebDriver
Mon Feb 13, 2017 2:35 pm by azharuddin

» How to integrate selenium with ZAPI-Zephyr
Sat Feb 11, 2017 2:25 am by gseera002c


Help with one driver instance across multiple tests

View previous topic View next topic Go down

Help with one driver instance across multiple tests

Post by FussyQBert on Sat May 14, 2011 12:45 am

I'm using TestNG and Selenium 2 to test my companies web application. I want to use one global instance of driver, so a new browser does not have to be opened every test. I was able to get this to work in Selenium 1, although everything in Selenium 1 took a lot more work Smile


class {
global driver;

method initDriver() {
if(driver == null) {
driver = new FirefoxDriver();

method teardownDriver() {

method testPage1() {
//screenshot page1

method testPage2() {
//navigate from page 1 to page 2
driver.find(byid).sendKeys(login); //fails here because element does not exist

//screenshot page 2

So it fails on the find element by id. I know its the right ID. If I move that line into the first test it sets the field just fine. Is it possible to have it work like this?

EDIT: Wow sorry, I had it all tabbed out, but it didnt keep the format Sad


Posts : 1
Join date : 2011-05-14

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

Permissions in this forum:
You cannot reply to topics in this forum