What do you mean by default instance inside of Seleno?


On Sun, Aug 4, 2013 at 7:37 PM, Robert Moore <notifications@github.com>wrote:

> In readme.md:
>
> > @@ -11,7 +11,14 @@ If you are upgrading to v0.4 from an earlier version then note that there are a
> >  	* If you are using ASP.NET MVC then there are some helper methods for that which require you to install MVC if you want to use them: Install-Package Microsoft.AspNet.Mvc
> >  	* If you installed MVC then you will also need to add binding redirects: Add-BindingRedirect
> >
> > -2. Create an assembly-level test fixture (if your unit test library supports it, otherwise creating a normal test fixture that will be guaranteed to run first should be enough because Seleno unloads itself when the app domain finishes) that looks something like this NUnit / ASP.NET web application example:
> > +2. Create a class that creates and holds a reference to an instance of SelenoHost. SelenoHost is your portal to Seleno. It does a lot of things, including running an IISExpress targeting the website you are testing, and as such is a relatively expective class to instantiate for each test. So you create one instance and use it in your tests (unless you want to point Seleno at multiple websites or multiple browsers in which case you will need one instance per website and browser):
>
> I assume expective was meant to be expensive?
>
> Given there is a default instance inside of Seleno, should we encourage
> them to use that by default?
>
> Thinking about it using the static constructor of their custom class is a
> great way of avoiding having to use some sort of assembly test fixture,
> which may or may not be supported by the test framework the person is using?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/TestStack/TestStack.Seleno/pull/78/files#r5569727>
> .
>