Free tools Windows power users keep installed
One-click scans. No signup required.
In Selenium with C#, the Page Object Model (POM) puts page-specific locators and actions in page or component classes, while tests keep assertions about application behavior. That division makes tests easier to read and localizes UI changes: update a locator in the page object rather than hunting for it across tests. It reduces duplication; it does not eliminate test maintenance.
What a page object should own
A page object is an object-oriented interface to a web page or a reusable part of one. It collects knowledge of the page’s HTML and locators and provides methods that express services a user or test can perform there. Selenium’s guidance describes the pattern in Java; the design principles apply in C#, but Java syntax should not be copied as if it were C#.
- Keep inside the object: locators for the page or component and methods that perform meaningful actions.
- Keep in the test: assertions about whether the application behaved as expected.
- Expose intention, not mechanics: a method such as
SubmitLoginis usually clearer than making every test issue low-level WebDriver commands.
Selenium’s guidance says, “Page objects themselves should never make verifications or assertions.” A narrow exception is checking that the expected page has loaded when its page object is created. That check verifies the object’s precondition; it should not replace the test’s assertion about the outcome under test. See Selenium’s Page Object Models documentation.
Set up Selenium for C#
Selenium’s getting-started instructions distinguish two .NET paths. The test-suite example lists .NET SDK 8.0 or later and uses dotnet restore and dotnet test. Its separate standalone, file-based HelloSelenium.cs path requires .NET 10 or later. The latter requirement does not apply to every Selenium C# project. Check the current instructions before choosing a setup, since SDK guidance can change: Write your first Selenium script.
#1 Best Overall
The official getting-started material describes a test project; exact project structure and package references depend on the chosen test framework and current template. Selenium’s .NET API documentation lists the Selenium.WebDriver and Selenium.Support modules. Use the current API reference for signatures rather than translating Java examples by guesswork: Selenium .NET API Docs.
Rider and Visual Studio Code are among the IDE options Selenium names. An IDE can help write and execute Selenium code, but neither is a Selenium requirement. See Organizing and Executing Selenium Code.
Build a page object and keep the assertion in the test
The following is an illustrative C# pattern, not a Selenium-provided class or a verified, executed sample. It uses Selenium’s familiar IWebDriver and By concepts; confirm signatures and package details against the API version in your project. Replace the sample selectors with selectors from your application.
using OpenQA.Selenium;
public sealed class LoginPage
{
private readonly IWebDriver driver;
private readonly By username = By.Id("username");
private readonly By password = By.Id("password");
private readonly By submit = By.CssSelector("button[type='submit']");
public LoginPage(IWebDriver driver)
{
this.driver = driver;
// Optional page-object precondition: confirm the expected page is loaded.
if (!driver.FindElement(username).Displayed)
{
throw new InvalidOperationException("Login page did not load.");
}
}
public HomePage LoginAs(string user, string secret)
{
driver.FindElement(username).SendKeys(user);
driver.FindElement(password).SendKeys(secret);
driver.FindElement(submit).Click();
return new HomePage(driver);
}
}
public sealed class HomePage
{
private readonly IWebDriver driver;
private readonly By greeting = By.CssSelector("[data-testid='greeting']");
public HomePage(IWebDriver driver) => this.driver = driver;
public string GreetingText => driver.FindElement(greeting).Text;
}The method names here—LoginAs and GreetingText—are illustrative, not Selenium-defined APIs. The test creates or receives the driver, passes it into the page object, calls the page’s service, and checks the application result:
var login = new LoginPage(driver);
var home = login.LoginAs("test-user", "example-password");
Assert.That(home.GreetingText, Is.EqualTo("Welcome, test-user"));The assertion framework and driver lifecycle depend on your test project. The important boundary is that the test states what success means; the page object knows how to interact with the page. Selenium recommends that public methods represent the services offered by a page or component, and that page objects seldom expose the underlying driver.
Represent an expected failed login without hiding its assertion
If a login attempt should fail, model the resulting page or state explicitly. For example, a method could submit credentials and return a login-page representation with an error-text property, or return a distinct error page object if navigation occurs. The test then asserts the expected error text. Keep the assertion out of the page object even when the object provides the method used to read that text.
Rank #3
Use component objects for repeated regions
A page object does not need to represent a whole page. If a navigation menu, account panel, or other region appears on several pages, give that region its own component object and compose it into each page. This keeps the component’s locator knowledge in one place without building a giant base class that obscures what each page can do.
public sealed class MainNavigation
{
private readonly IWebDriver driver;
private readonly By accountLink = By.CssSelector("a[href='/account']");
public MainNavigation(IWebDriver driver) => this.driver = driver;
public void OpenAccount() => driver.FindElement(accountLink).Click();
}
public sealed class HomePageWithNavigation
{
public MainNavigation Navigation { get; }
public HomePageWithNavigation(IWebDriver driver)
{
Navigation = new MainNavigation(driver);
}
}This composition is a design illustration. Choose components around coherent, repeated services rather than splitting every visual element into a class. Avoid exposing a general-purpose driver surface through every page object; tests that need unrestricted WebDriver operations can otherwise bypass the interface the model is meant to provide.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Choose a structure that keeps tests understandable
There is no single class layout that fits every application. Evaluate the design by whether it reduces duplicated locator and HTML knowledge, keeps tests readable, reuses genuinely repeated regions, and leaves assertions visible in test code.
- If tests repeat selectors and click sequences, move that page-specific knowledge into a page object.
- If the same coherent region appears across pages, consider a component object and compose it.
- If a page class becomes a collection of unrelated low-level commands, narrow its public methods to meaningful page services.
- If a base class or helper hides the behavior a test performs, prefer explicit composition or a clearer page method.
Troubleshoot common POM problems
A locator fails after a UI change
Update the locator in the page or component that owns it, then check whether the page’s services and the affected tests still describe the current UI. POM localizes locator maintenance; it cannot prevent changes to application behavior from requiring test updates.
The page object throws while it is being constructed
First confirm that the test navigated to the expected page before creating the object. Then verify that the chosen locator matches the current page and that the element is present when the constructor checks it. Keep constructor checks narrow: they should establish that the object represents the expected page, not assert the test’s business outcome.
Tests contain many raw WebDriver calls
Move repeated, page-specific interactions behind intention-revealing methods. Do not abstract every WebDriver call automatically; a page object is useful when its methods express a service and make tests clearer.
Best Value
- Used Book in Good Condition
Assertions are buried in page methods
Return the information or page representation the test needs, then assert in the test. For a successful login, for example, return a home-page object and assert its visible result. For a failed login, expose the error state or text and assert that it matches expectations.
Java sample code does not compile in C#
The Selenium Page Object Models page illustrates the pattern in Java, not a C# implementation. Consult the .NET API reference for C# types, namespaces, and signatures, and treat translated examples as design guidance rather than compile-ready code.
Or skip the browser setup
If the task is capturing a website image or PDF rather than building an interactive browser test, ScreenshotNeo offers a one-call screenshot API and an MCP server. This does not replace Selenium POM for testing application behavior. A capture request can look like this (see the ScreenshotNeo API documentation):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Create a free ScreenshotNeo account to try 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
