Seleno helps you to write automated UI tests in the right way by implementing Page Objects and Page Components and by reading and writing web page data using strongly typed view models. It uses Selenium Web Driver for browser automation.
If you are upgrading from an earlier version then note that there are a number of breaking changes that you need to take into account.
-
Install-Package TestStack.Seleno
- 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
-
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 expensive 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):
public static class Host { public static readonly SelenoHost Instance = new SelenoHost(); static Host() { Instance.Run("Name.Of.Your.Web.Project", 12346, c => c .UsingLoggerFactory(new ConsoleFactory()) // If you are using MVC then do this where RouteConfig is the class that registers your routes in the "Name.Of.Your.Web.Project" project // If you aren't using MVC then don't include this line .WithRouteConfig(RouteConfig.RegisterRoutes) ); } }Name.Of.Your.Web.Projectis the path to the web project relative to the solution, not the name of the project or the assembly - if this is incorrect it may throw aDirectoryNotFoundException- The
123456is the port number you want the site to run on - it can be anything you want, just make it unique and unused - The
cvariable is a fluent configurator - chain method calls off of it to configure the different parts of Seleno - By default it uses Firefox so you will need to install that
- You might need to run Visual Studio / your test runner as an admin if you can an error when the port tries to get registered by IIS Express
-
Create page objects by extending
Page, or if you want to use strongly-typed view models,Page<T>, e.g.:public class HomePage : Page { public Form1Page GoToRegisterPage() { return Navigate.To<RegisterPage>(By.LinkText("Register")); } } public class RegisterPage : Page<RegisterModel> { public HomePage RegisterUser(RegisterModel registerModel) { Input.Model(registerModel); return Navigate.To<HomePage>(By.CssSelector("input[type=submit]")); } }- Seleno provides a DSL that hides most of Selenium Web Driver from you. Feel free to make use of intellisense within your page object to experiment with what's possible
- There are some links to advanced usage instructions and tutorials below
-
If you want to wrap common components of your pages then create components by extending
UiComponent, e.g.:public class HomePage : Page { ... public LoginPanel LoginPanel { get { return GetComponent<LoginPanel>(); } } } public class LoginPanel : UiComponent { public bool IsLoggedIn { get { return Find.OptionalElement(By.Id("login-panel")) == null; } } public string LoggedInUserName { get { return Find.Element(By.Id("login-username")).Text; } } } -
Create automated tests that use your page objects, e.g. this NUnit example:
class RegistrationTests { [Test] public void GivenAUserIsntRegistered_WhenRegisteringThem_TheyEndUpBackOnTheHomepageAndLoggedIn() { var page = Host.Instance.NavigateToInitialPage<HomePage>() .GoToRegisterPage() .RegisterUser(ObjectMother.NewUser); Assert.That(page.Title, Is.EqualTo("Home")); Assert.That(page.LoginPanel.IsLoggedIn, Is.True); Assert.That(page.LoginPanel.LoggedInUserName, Is.EqualTo(ObjectMother.NewUser.UserName)); } }
Check out our documentation.
The Page Object design pattern is a way of encapsulating the interaction with an individual page in your application in a single object. It makes heavy use of OO principles to enable code reuse and improve maintenance. Rather than having tests that are a series of Selenium commands that are sent to the server, your tests become a series of interactions with objects that represent a page (or part of one).
The usage of the Page Object design pattern creates a strong separation of concerns between tests and Page Objects. The tests specify what should happen and the Page Objects encapsulate how it happens.
- Tests are very procedural. They only interact with the Page Objects and make assertions. They should not have any implementation details, such as Selenium calls, whatsoever.
- Page Objects encapsulate all of the interaction with Selenium, and all of the logic of that interaction. There are no test assertions in the Page Objects but they can throw exceptions.
- Separating test specification from test implementation makes tests more robust. If you change how a feature works, you just have to change the test, rather than every test that uses the feature.
- Maintenance is easier because you only have to change things in one place.
- Tests are more readable as they just work with Page Objects and make assertions. They do not have any Selenium code as this is hidden away in the Page Object.
- Mehdi Khalili (@MehdiK)
- Michael Whelan (@mwhelan)
- Rob Moore (@robdmoore)
- Franck Theolade (@Gwayaboy)
- Rhys Campbell (@RhysC)
If you have any problems with Seleno, please raise an issue. We are also happy to take pull requests; if you are thinking of contributing a major change feel free to raise an issue first and we can talk through and provide assistance.