C#/.NET web UI test automation full featured framework based on Selenium WebDriver. It uses fluent page object pattern.

The package targets .NET Standard 2.0, which supports .NET 5+, .NET Framework 4.6.1+ and .NET Core/Standard 2.0+.

• What's new in v3.0.0
• Migrating to Atata 3

• WebDriver. Based on Selenium WebDriver and preserves all its features.
• Page Object Model. Provides unique fluent page object pattern that is easy to implement and maintain.
• Components. Contains a rich set of ready to use components for inputs, tables, lists, etc.
• Integration. Works on any .NET test engine (e.g. NUnit, xUnit, SpecFlow) as well as on CI systems like Jenkins, GitHub Actions or TeamCity.
• Triggers. A bunch of triggers to bind with different events to extend component behavior.
• Verification. A set of fluent assertion methods and triggers for a component and data verification.
• Configurable. Defines the default component search strategies as well as additional settings. Atata.Configuration.Json provides flexible JSON configurations.
• Reporting/Logging. Built-in customizable logging; screenshots and snapshots capturing functionality.
• Extensible. Atata.Bootstrap and Atata.KendoUI packages have a set of ready to use components. Framework supports any kind of extending.

Simple sign-in page object for https://demo.atata.io/signin page:

using Atata;

namespace SampleApp.UITests
{
    using _ = SignInPage;

    [Url("signin")] // Relative URL of the page.
    [VerifyH1] // Verifies that H1 header text equals "Sign In" upon page object initialization.
    public class SignInPage : Page<_>
    {
        [FindByLabel] // Finds <label> element containing "Email" (<label for="email">Email</label>), then finds text <input> element by "id" that equals label's "for" attribute value.
        public TextInput<_> Email { get; private set; }

        [FindById("password")] // Finds password <input> element by id that equals "password" (<input id="password" type="password">).
        public PasswordInput<_> Password { get; private set; }

        [FindByValue(TermCase.Title)] // Finds button element by value that equals "Sign In" (<input value="Sign In" type="submit">).
        public Button<_> SignIn { get; private set; }
    }
}

Usage in the test method:

[Test]
public void SignIn()
{
    Go.To<SignInPage>()
        .Email.Set("[email protected]")
        .Password.Set("abc123")
        .SignIn.Click();
}

[SetUp]
public void SetUp()
{
    AtataContext.Configure()
        .UseChrome()
        .UseBaseUrl("https://demo.atata.io/")
        .Build();
}

Find out more on Atata usage. Check atata-framework/atata-samples for different Atata test scenario samples.

Demo atata-framework/atata-sample-app-tests UI tests application demonstrates different testing approaches and features of Atata Framework. It covers main Atata features: page navigation, data input and verification, interaction with pop-ups and tables, logging, screenshot capture, etc.

Sample test:

[Test]
public void Create()
{
    Login()
        .New()
            .ModalTitle.Should.Be("New User")
            .General.FirstName.SetRandom(out string firstName)
            .General.LastName.SetRandom(out string lastName)
            .General.Email.SetRandom(out string email)
            .General.Office.SetRandom(out Office office)
            .General.Gender.SetRandom(out Gender gender)
            .Save()
        .GetUserRow(email).View()
            .AggregateAssert(x => x
                .Header.Should.Be($"{firstName} {lastName}")
                .Email.Should.Be(email)
                .Office.Should.Be(office)
                .Gender.Should.Be(gender)
                .Birthday.Should.Not.Exist()
                .Notes.Should.Not.Exist());
}

Find out more on Atata Docs and on Getting Started page in particular.

You can also check the following tutorials:

• Atata - C# Web Test Automation Framework - an introduction to Atata Framework.
• Verification of Page - how to verify web page data using different approaches of Atata Framework.
• Verification of Validation Messages - how to verify validation messages on web pages using Atata Framework.
• Handle Confirmation Popups - how to handle different confirmation popups using Atata Framework.
• Multi-Browser Configuration via .runsettings files - how to configure multi-browser tests application using .runsettings files.
• Reporting to Extent Reports - how to configure Atata reporting to Extent Reports.

Feel free to ask any questions regarding Atata Framework. Any feedback, issues and feature requests are welcome.

You can ask a question on Stack Overflow using atata tag.

If you faced an issue please report it to Atata Issues, write to Slack or just mail to [email protected].

• Stack Overflow: https://stackoverflow.com/questions/tagged/atata
• Slack: https://atata-framework.slack.com
• Atata Issues: https://github.com/atata-framework/atata/issues
• Twitter: https://twitter.com/AtataFramework
• YouTube: https://www.youtube.com/@atataframework

Contact me if you need a help in test automation using Atata Framework, or if you are looking for a quality test automation implementation for your project.

• Email: [email protected]
• Skype: e.shunevich
• LinkedIn: https://www.linkedin.com/in/yevgeniy-shunevych

Check out Contributing Guidelines for details.

Atata Framework tries to follow Semantic Versioning 2.0 when possible. Sometimes Selenium.WebDriver dependency package can contain breaking changes in minor version releases, so those changes can break Atata as well. But Atata manages its sources according to SemVer. Thus backward compatibility is mostly followed and updates within the same major version (e.g. from 2.1 to 2.2) should not require code changes.

Atata is an open source software, licensed under the Apache License 2.0. See LICENSE for details.