Comments on: WatiN Patterns #1: No Browser Left Behind http://www.richardlawrence.info/2009/02/04/watin-patterns-1-no-browser-left-behind/ On making software teams happier and more productive Fri, 03 Feb 2012 10:41:13 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Richard http://www.richardlawrence.info/2009/02/04/watin-patterns-1-no-browser-left-behind/comment-page-1/#comment-24 Richard Sat, 03 Jul 2010 05:17:38 +0000 http://www.richardlawrence.info/?p=119#comment-24 @Nick - True, as the test suite gets large, you may need to share a browser instance between tests (assuming browser start-up is the bottleneck for you). Tests shouldn't have to worry about whether the browser is in a good starting state, though, so I usually recommend replacing IE with a class of your own that implements IDisposable and has an IE. That class would take responsibility for creating the IE instance when necessary in its constructor and resetting state in Dispose. Perhaps I'll write about this in more detail sometime if there's interest. Also, since this post, I've changed from using WatiN with NUnit or MSTest to using it with Cuke4Nuke. This changes the patterns somewhat. @Nick – True, as the test suite gets large, you may need to share a browser instance between tests (assuming browser start-up is the bottleneck for you). Tests shouldn’t have to worry about whether the browser is in a good starting state, though, so I usually recommend replacing IE with a class of your own that implements IDisposable and has an IE. That class would take responsibility for creating the IE instance when necessary in its constructor and resetting state in Dispose. Perhaps I’ll write about this in more detail sometime if there’s interest.

Also, since this post, I’ve changed from using WatiN with NUnit or MSTest to using it with Cuke4Nuke. This changes the patterns somewhat.

]]> By: Nick http://www.richardlawrence.info/2009/02/04/watin-patterns-1-no-browser-left-behind/comment-page-1/#comment-23 Nick Fri, 25 Jun 2010 17:18:20 +0000 http://www.richardlawrence.info/?p=119#comment-23 A using statement is fine if you want to open and close a browser for every unit test. This will become very time consuming as the number of tests grow. A using statement is fine if you want to open and close a browser for every unit test. This will become very time consuming as the number of tests grow.

]]>