NUnit Setup seems to not call WebDriver after first test completes - selenium

Question

I'm running into an issue that seems to be related to webdriver/nunit.
On the initial running my first test [Setup] and [Teardown] work. When the system tries to run my next test, which requires a [Setup] it doesn't seem as though the WebDriver is called.
[SetUp]
//This has to be done for all tests. It is the setup I say!
public void Setup()
{
LaunchBrowser();
driver.Manage().Timeouts().ImplicitlyWait(TimeSpan.FromSeconds(45));
}
[TearDown]
//This has to be done for all tests. It is the teardown I say!
public void TearItDown()
{
driver.Dispose();
}
If I comment out the [Teardown], all my tests run no problem.
LaunchBrowser()
public static IWebDriver driver = new InternetExplorerDriver();
public string landingPage = "http://www.smartdrive.net";
public void LaunchBrowser()
{
driver.Navigate().GoToUrl(landingPage);
}
I have tried on the last test to add a driver.Dispose(); figuring I could just close the session once all tests run, but it doesn't seem to do the trick.
error I receive with [Teardown] in place
Result Message:
OpenQA.Selenium.WebDriverException : Unexpected error. System.Net.WebException: Unable to connect to the remote server --->
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:51089
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at OpenQA.Selenium.Remote.HttpCommandExecutor.Execute(Command commandToExecute)
at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
Result StackTrace:
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.Remote.RemoteWebDriver.FindElement(String mechanism, String value)
at OpenQA.Selenium.By.FindElement(ISearchContext context)
at UnitTestProject1.Browser_Landing.getLandingPlacement() in c:\Users\erikag\Desktop\AutomationTests\VS_NetSeleniumTest\UnitTestProject1\UnitTestProject1\Browser_Landing.cs:line 30
at UnitTestProject1.ServiceConsoleTest.PlacementChk() in c:\Users\erikag\Desktop\AutomationTests\VS_NetSeleniumTest\UnitTestProject1\UnitTestProject1\TestSuite_LandLog.cs:line 46
I did read somewhere that the issue was correlated to the webdriver having issues relaunching after the the [Teardown], but I can't seem to figure out how to work around this.

Answer 1

You are disposing the driver after every run but not instantiating before each run. So driver won't work as expected. Instantiate the driver inside LaunchBrowser() method and re-run the tests
Just more info Dispose() resets the diver and, thus the instance is not valid anymore with the code block you posted. See this
And, best practice is probably using Quit instead of Dispose because Quit() calls Dispose and does some more clean up so you don't have to use Dispose separately.
And, with the change the LaunchBrowser() method should look like the following:
public IWebDriver Driver;
public string landingPage = "http://www.smartdrive.net";
public void LaunchBrowser()
{
driver = new InternetExplorerDriver();
driver.Navigate().GoToUrl(landingPage);
}