Skip to content

About

πŸš€ A robust, maintainable C# Selenium automation framework using NUnit, designed for efficient functional and regression testing with built-in reporting and logging.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

C#-Selenium Automation Framework

A comprehensive, scalable, and maintainable test automation framework built with Selenium WebDriver and C# .NET 10. Designed for enterprise-grade web application testing with support for CI/CD integration, detailed reporting, and future MCP (Model Context Protocol) extensibility.

.NET Selenium NUnit License


πŸš€ Quick Start

Get up and running in 5 minutes:

# 1. Clone the repository
git clone https://github.com/amitbad/CSharp-Selenium-Test-Automation.git
cd Test-Automation-CS-Selenium

# 2. Restore dependencies
dotnet restore

# 3. Build the solution
dotnet build

# 4. Update the base URL in appsettings.json
# Edit: tests/TestAutomation.Tests/appsettings.json
# Change "BaseUrl" to your application URL

# 5. Run tests
dotnet test

# 6. Run specific test categories
dotnet test --filter "Category=API"      # API tests only
dotnet test --filter "Category=UI"       # UI tests only
dotnet test --filter "Category=Smoke"    # Smoke tests

# 7. Run headless (for CI/CD)
TEST_AUTO_HEADLESS=true dotnet test

# 8. View the report
open tests/TestAutomation.Tests/Reports/TestReport_*.html

That's it! For detailed documentation, continue reading below.


πŸ“‹ Table of Contents


✨ Features

Core Features

  • Selenium WebDriver 4.25 - Latest Selenium with modern browser support
  • REST API Testing - Built-in API client with RestSharp for hybrid testing
  • NUnit 4.2 - Industry-standard .NET testing framework with rich attributes
  • FluentAssertions - Readable, expressive assertion syntax
  • Page Object Model (POM) - Clean separation of test logic and page interactions
  • JSON-based Locators - Externalized, maintainable element locators
  • Multi-browser Support - Chrome, Firefox, Edge, Safari
  • Parallel Test Execution - Thread-safe driver management
  • Automatic Driver Management - WebDriverManager handles driver binaries
  • Data-Driven Testing - TestCase, TestCaseSource for parameterized tests
  • Hybrid Testing - Combine API and UI tests for faster, more reliable E2E tests

Configuration & Environment

  • Environment-based Configuration - Separate configs for Dev, Staging, Production
  • Environment Variable Override - CI/CD friendly configuration
  • Secure Secrets Management - No hardcoded credentials

Reporting & Logging

  • Extent Reports - Beautiful HTML reports with screenshots
  • Serilog Logging - Structured logging to console and file
  • Screenshot on Failure - Automatic screenshot capture

CI/CD Ready

  • GitHub Actions - Pre-configured workflows
  • Jenkins Pipeline - Jenkinsfile included
  • Docker Support - Ready for containerized execution

Future Ready

  • MCP Integration Foundation - Prepared for AI-assisted testing
  • Extensible Architecture - Easy to add new capabilities

πŸ— Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                        Test Layer                                β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”              β”‚
β”‚  β”‚ SampleTests β”‚  β”‚ LoginTests  β”‚  β”‚ OtherTests  β”‚              β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜              β”‚
β”‚         β”‚                β”‚                β”‚                      β”‚
β”‚         β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜                      β”‚
β”‚                          β–Ό                                       β”‚
β”‚                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”                                β”‚
β”‚                   β”‚  BaseTest   β”‚                                β”‚
β”‚                   β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜                                β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                           β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                    Page Layer                                    β”‚
β”‚         β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”                      β”‚
β”‚         β–Ό                β–Ό                β–Ό                      β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”              β”‚
β”‚  β”‚  LoginPage  β”‚  β”‚  HomePage   β”‚  β”‚ OtherPages  β”‚              β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜              β”‚
β”‚         β”‚                β”‚                β”‚                      β”‚
β”‚         β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜                      β”‚
β”‚                          β–Ό                                       β”‚
β”‚                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”                                β”‚
β”‚                   β”‚  BasePage   β”‚                                β”‚
β”‚                   β””β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜                                β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                           β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                  Framework Layer                                 β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚                                                          β”‚   β”‚
β”‚  β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”      β”‚   β”‚
β”‚  β”‚  β”‚   Driver    β”‚  β”‚  Locators   β”‚  β”‚  Reporting  β”‚      β”‚   β”‚
β”‚  β”‚  β”‚  Manager    β”‚  β”‚ Repository  β”‚  β”‚   Manager   β”‚      β”‚   β”‚
β”‚  β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜      β”‚   β”‚
β”‚  β”‚                                                          β”‚   β”‚
β”‚  β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”      β”‚   β”‚
β”‚  β”‚  β”‚   Config    β”‚  β”‚   Logger    β”‚  β”‚  Utilities  β”‚      β”‚   β”‚
β”‚  β”‚  β”‚  Manager    β”‚  β”‚             β”‚  β”‚             β”‚      β”‚   β”‚
β”‚  β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜      β”‚   β”‚
β”‚  β”‚                                                          β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ–₯️ Cross-Platform Support

This framework is fully cross-platform and works on Windows, macOS, and Linux.

Platform Compatibility

Component Windows macOS Linux
.NET 10 SDK βœ… βœ… βœ…
Selenium WebDriver βœ… βœ… βœ…
Chrome βœ… βœ… βœ…
Firefox βœ… βœ… βœ…
Edge βœ… βœ… βœ…
Safari ❌ βœ… ❌
GitHub Actions βœ… βœ… βœ…
Jenkins βœ… βœ… βœ…

Why It Works Everywhere

  • .NET 10 is cross-platform (runs natively on all OS)
  • WebDriverManager automatically downloads correct browser drivers per OS
  • Path handling uses Path.Combine() for OS-agnostic paths
  • No platform-specific code in the framework

πŸ“‹ Prerequisites

Required

.NET 10 Installation Per Platform

Windows

# Using winget
winget install Microsoft.DotNet.SDK.10

# Or download installer from https://dotnet.microsoft.com/download

macOS

# Using Homebrew
brew install dotnet@10

# Or download installer from https://dotnet.microsoft.com/download

Linux (Ubuntu/Debian)

# Add Microsoft package repository
wget https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb

# Install .NET 10 SDK
sudo apt-get update
sudo apt-get install -y dotnet-sdk-10.0

# For headless Chrome testing, install dependencies
sudo apt-get install -y chromium-browser

Browsers (at least one)

  • Google Chrome (recommended)
  • Mozilla Firefox
  • Microsoft Edge
  • Safari (macOS only)

Verify Installation

# Check .NET version (works on all platforms)
dotnet --version
# Expected: 10.0.x

# Check Git
git --version

πŸš€ Installation

1. Clone the Repository

git clone https://github.com/yourusername/Test-Automation-CS-Selenium.git
cd Test-Automation-CS-Selenium

2. Restore Dependencies

dotnet restore

3. Build the Solution

dotnet build

4. Configure Environment

# Copy example environment file
cp .env.example .env

# Edit .env with your settings
# Update appsettings.json with your application URL

5. Run Tests

dotnet test

πŸ“ Project Structure

Test-Automation-CS-Selenium/
β”œβ”€β”€ .github/
β”‚   └── workflows/
β”‚       β”œβ”€β”€ test.yml                 # Main CI workflow
β”‚       └── scheduled-tests.yml      # Scheduled regression tests
β”œβ”€β”€ src/
β”‚   └── TestAutomation.Framework/
β”‚       β”œβ”€β”€ Api/                         # API Testing
β”‚       β”‚   β”œβ”€β”€ ApiClient.cs             # REST client wrapper
β”‚       β”‚   β”œβ”€β”€ ApiResponse.cs           # Response models
β”‚       β”‚   β”œβ”€β”€ ApiAssertions.cs         # Fluent assertions
β”‚       β”‚   └── Models/                  # Request/Response models
β”‚       β”‚       β”œβ”€β”€ AuthModels.cs
β”‚       β”‚       └── CommonModels.cs
β”‚       β”œβ”€β”€ Configuration/
β”‚       β”‚   β”œβ”€β”€ ConfigurationManager.cs
β”‚       β”‚   └── TestSettings.cs
β”‚       β”œβ”€β”€ Driver/
β”‚       β”‚   β”œβ”€β”€ BrowserType.cs
β”‚       β”‚   β”œβ”€β”€ DriverFactory.cs
β”‚       β”‚   └── DriverManager.cs
β”‚       β”œβ”€β”€ Locators/
β”‚       β”‚   β”œβ”€β”€ ElementLocator.cs
β”‚       β”‚   β”œβ”€β”€ LocatorRepository.cs
β”‚       β”‚   β”œβ”€β”€ LocatorType.cs
β”‚       β”‚   └── PageLocators.cs
β”‚       β”œβ”€β”€ Logging/
β”‚       β”‚   └── Logger.cs
β”‚       β”œβ”€β”€ MCP/
β”‚       β”‚   β”œβ”€β”€ IMcpClient.cs
β”‚       β”‚   β”œβ”€β”€ McpTestContext.cs
β”‚       β”‚   └── McpIntegrationReadme.md
β”‚       β”œβ”€β”€ Pages/
β”‚       β”‚   └── BasePage.cs
β”‚       β”œβ”€β”€ Reporting/
β”‚       β”‚   └── ExtentReportManager.cs
β”‚       β”œβ”€β”€ Utilities/
β”‚       β”‚   β”œβ”€β”€ RetryHelper.cs
β”‚       β”‚   β”œβ”€β”€ TestDataHelper.cs
β”‚       β”‚   └── WaitHelper.cs
β”‚       └── TestAutomation.Framework.csproj
β”œβ”€β”€ tests/
β”‚   └── TestAutomation.Tests/
β”‚       β”œβ”€β”€ Base/
β”‚       β”‚   └── BaseTest.cs
β”‚       β”œβ”€β”€ Locators/
β”‚       β”‚   β”œβ”€β”€ LoginPage.json
β”‚       β”‚   └── HomePage.json
β”‚       β”œβ”€β”€ Pages/
β”‚       β”‚   β”œβ”€β”€ LoginPage.cs
β”‚       β”‚   └── HomePage.cs
β”‚       β”œβ”€β”€ TestData/
β”‚       β”‚   └── users.json
β”‚       β”œβ”€β”€ Tests/
β”‚       β”‚   β”œβ”€β”€ API/                 # API tests
β”‚       β”‚   β”‚   β”œβ”€β”€ SampleApiTests.cs
β”‚       β”‚   β”‚   └── AuthApiTests.cs
β”‚       β”‚   β”œβ”€β”€ UI/                  # UI tests
β”‚       β”‚   β”‚   β”œβ”€β”€ SampleTests.cs
β”‚       β”‚   β”‚   └── LoginTests.cs
β”‚       β”‚   └── Hybrid/              # Combined API + UI tests
β”‚       β”‚       └── HybridTestExample.cs
β”‚       β”œβ”€β”€ appsettings.json
β”‚       β”œβ”€β”€ appsettings.Development.json
β”‚       β”œβ”€β”€ appsettings.Staging.json
β”‚       β”œβ”€β”€ appsettings.Production.json
β”‚       └── TestAutomation.Tests.csproj
β”œβ”€β”€ .env.example
β”œβ”€β”€ .gitignore
β”œβ”€β”€ docker-compose.yml           # Selenium Grid setup
β”œβ”€β”€ TestAutomation.sln
β”œβ”€β”€ Jenkinsfile
└── README.md

βš™οΈ Configuration

Configuration Files

File Purpose
appsettings.json Default configuration
appsettings.Development.json Development environment overrides
appsettings.Staging.json Staging environment overrides
appsettings.Production.json Production environment overrides

Configuration Options

{
  "TestSettings": {
    "BaseUrl": "https://your-app.com",
    "Browser": "Chrome",
    "Headless": false,
    "ImplicitWaitSeconds": 10,
    "ExplicitWaitSeconds": 30,
    "PageLoadTimeoutSeconds": 60,
    "MaximizeWindow": true,
    "ScreenshotOnFailure": true,
    "ScreenshotPath": "Screenshots",
    "ReportPath": "Reports",
    "Environment": "Development",
    "EnableDetailedLogging": true,
    "RetryCount": 0,
    "UseRemoteDriver": false,
    "RemoteWebDriverUrl": null
  }
}

Environment Variables

Environment variables override configuration files. Prefix with TEST_AUTO_:

Variable Description Example
TEST_ENVIRONMENT Environment name Staging
TEST_AUTO_BASE_URL Application URL https://staging.app.com
TEST_AUTO_BROWSER Browser to use Chrome, Firefox, Edge
TEST_AUTO_HEADLESS Headless mode true, false
TEST_AUTO_USE_REMOTE_DRIVER Use Selenium Grid true, false
TEST_AUTO_REMOTE_WEBDRIVER_URL Grid URL http://localhost:4444/wd/hub

Setting Environment Variables

# Linux/macOS
export TEST_ENVIRONMENT=Staging
export TEST_AUTO_BASE_URL=https://staging.example.com
export TEST_AUTO_HEADLESS=true

# Windows PowerShell
$env:TEST_ENVIRONMENT = "Staging"
$env:TEST_AUTO_BASE_URL = "https://staging.example.com"
$env:TEST_AUTO_HEADLESS = "true"

# Windows CMD
set TEST_ENVIRONMENT=Staging
set TEST_AUTO_BASE_URL=https://staging.example.com
set TEST_AUTO_HEADLESS=true

πŸ§ͺ NUnit Testing Framework

This framework uses NUnit 4.2 as the testing framework along with FluentAssertions for readable assertions.

NUnit Packages Included

Package Version Purpose
NUnit 4.2.2 Core testing framework
NUnit3TestAdapter 4.6.0 Test discovery and execution
NUnit.Analyzers 4.4.0 Code analysis for best practices
Microsoft.NET.Test.Sdk 17.12.0 .NET test SDK
FluentAssertions 6.12.1 Fluent assertion syntax
coverlet.collector 6.0.2 Code coverage collection

NUnit Attributes Reference

Test Class Attributes

Attribute Description Example
[TestFixture] Marks a class as containing tests [TestFixture]
[TestFixtureSetUp] One-time setup for the fixture [OneTimeSetUp]
[TestFixtureTearDown] One-time teardown for the fixture [OneTimeTearDown]
[SetUp] Runs before each test [SetUp]
[TearDown] Runs after each test [TearDown]
[Parallelizable] Enable parallel execution [Parallelizable(ParallelScope.Self)]

Test Method Attributes

Attribute Description Example
[Test] Marks a method as a test [Test]
[TestCase] Data-driven test with inline data [TestCase("user", "pass")]
[TestCaseSource] Data-driven test with external source [TestCaseSource(nameof(TestData))]
[Category] Categorize tests for filtering [Category("Smoke")]
[Description] Add test description [Description("Verify login")]
[Ignore] Skip a test [Ignore("Bug #123")]
[Retry] Retry failed tests [Retry(3)]
[Timeout] Set test timeout [Timeout(30000)]
[Order] Control test execution order [Order(1)]

NUnit Assertions vs FluentAssertions

// NUnit Classic Assertions
Assert.That(actual, Is.EqualTo(expected));
Assert.That(list, Has.Count.EqualTo(5));
Assert.That(value, Is.GreaterThan(10));
Assert.IsTrue(condition);
Assert.IsNotNull(obj);

// FluentAssertions (Recommended - more readable)
actual.Should().Be(expected);
list.Should().HaveCount(5);
value.Should().BeGreaterThan(10);
condition.Should().BeTrue();
obj.Should().NotBeNull();

// String assertions
text.Should().Contain("expected");
text.Should().StartWith("Hello");
text.Should().MatchRegex(@"\d+");

// Collection assertions
list.Should().Contain(item);
list.Should().BeInAscendingOrder();
list.Should().OnlyContain(x => x > 0);

// Exception assertions
action.Should().Throw<InvalidOperationException>()
      .WithMessage("*error*");

Test Lifecycle in This Framework

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                    Test Execution Flow                       β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                                              β”‚
β”‚  [OneTimeSetUp] ─────► Initialize Logger                    β”‚
β”‚        β”‚               Log test suite start                  β”‚
β”‚        β–Ό                                                     β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚  For Each Test:                                       β”‚   β”‚
β”‚  β”‚                                                       β”‚   β”‚
β”‚  β”‚  [SetUp] ──────► Create Extent Report test           β”‚   β”‚
β”‚  β”‚      β”‚           Initialize WebDriver                 β”‚   β”‚
β”‚  β”‚      β”‚           Log test start                       β”‚   β”‚
β”‚  β”‚      β–Ό                                                β”‚   β”‚
β”‚  β”‚  [Test] ───────► Execute test steps                  β”‚   β”‚
β”‚  β”‚      β”‚           Use Page Objects                     β”‚   β”‚
β”‚  β”‚      β”‚           Perform assertions                   β”‚   β”‚
β”‚  β”‚      β–Ό                                                β”‚   β”‚
β”‚  β”‚  [TearDown] ───► Log test result                     β”‚   β”‚
β”‚  β”‚                  Take screenshot (on failure)         β”‚   β”‚
β”‚  β”‚                  Quit WebDriver                       β”‚   β”‚
β”‚  β”‚                  Update Extent Report                 β”‚   β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β”‚        β”‚                                                     β”‚
β”‚        β–Ό                                                     β”‚
β”‚  [OneTimeTearDown] ─► Flush Extent Report                   β”‚
β”‚                       Close Logger                           β”‚
β”‚                       Generate HTML report                   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Parallel Test Execution

Enable parallel execution at different levels:

// Parallel at assembly level (in AssemblyInfo.cs or test file)
[assembly: Parallelizable(ParallelScope.Fixtures)]
[assembly: LevelOfParallelism(4)]

// Parallel at fixture level
[TestFixture]
[Parallelizable(ParallelScope.Self)]
public class MyTests : BaseTest { }

// Parallel at test level
[Test]
[Parallelizable(ParallelScope.Self)]
public void MyTest() { }

ParallelScope Options:

  • None - No parallel execution
  • Self - Test/fixture can run in parallel with others
  • Children - Child tests can run in parallel
  • Fixtures - Fixtures can run in parallel
  • All - Maximum parallelism

Test Data Sources

// Inline TestCase
[Test]
[TestCase("admin", "admin123", true)]
[TestCase("user", "wrongpass", false)]
public void LoginTest(string user, string pass, bool expected) { }

// TestCaseSource with method
[Test]
[TestCaseSource(nameof(GetLoginTestData))]
public void LoginTest(string user, string pass, bool expected) { }

private static IEnumerable<TestCaseData> GetLoginTestData()
{
    yield return new TestCaseData("admin", "admin123", true)
        .SetName("Admin Login")
        .SetCategory("Smoke");
    yield return new TestCaseData("user", "wrong", false)
        .SetName("Invalid Login")
        .SetCategory("Negative");
}

// TestCaseSource with external class
[Test]
[TestCaseSource(typeof(LoginTestData), nameof(LoginTestData.ValidLogins))]
public void ValidLoginTest(string user, string pass) { }

✍️ Writing Tests

Basic Test Structure

using NUnit.Framework;
using FluentAssertions;
using TestAutomation.Tests.Base;
using TestAutomation.Framework.Driver;

namespace TestAutomation.Tests.Tests;

[TestFixture]
[Category("Smoke")]
public class MyTests : BaseTest
{
    [Test]
    [Description("Verify home page loads successfully")]
    public void VerifyHomePageLoads()
    {
        // Arrange
        LogStep("Navigate to home page");
        NavigateToBaseUrl();

        // Act
        var title = DriverManager.GetPageTitle();

        // Assert
        title.Should().NotBeNullOrEmpty();
        LogInfo($"Page title: {title}");
    }
}

Data-Driven Tests

[Test]
[TestCase("user1@test.com", "password1", true)]
[TestCase("invalid@test.com", "wrong", false)]
public void LoginTest(string username, string password, bool shouldSucceed)
{
    var loginPage = new LoginPage();
    loginPage.NavigateToLoginPage();
    
    if (shouldSucceed)
    {
        var homePage = loginPage.Login(username, password);
        homePage.IsUserLoggedIn().Should().BeTrue();
    }
    else
    {
        loginPage.EnterUsername(username);
        loginPage.EnterPassword(password);
        loginPage.ClickLoginButton();
        loginPage.IsErrorMessageDisplayed().Should().BeTrue();
    }
}

Test Categories

Use categories to organize and filter tests:

[Test]
[Category("Smoke")]      // Quick sanity tests
[Category("Regression")] // Full regression suite
[Category("Login")]      // Feature-specific
public void MyTest() { }

πŸ“„ Page Object Model

Creating a Page Object

using OpenQA.Selenium;
using TestAutomation.Framework.Pages;
using TestAutomation.Framework.Logging;

namespace TestAutomation.Tests.Pages;

public class ProductPage : BasePage
{
    // Required: Page name for locator lookup
    protected override string PageName => "ProductPage";

    // Fallback locators (if JSON not available)
    private static class Locators
    {
        public static By ProductTitle => By.CssSelector(".product-title");
        public static By AddToCartButton => By.Id("add-to-cart");
        public static By PriceLabel => By.CssSelector(".price");
    }

    // Page methods using fluent pattern
    public ProductPage NavigateToProduct(string productId)
    {
        Logger.Step($"Navigating to product: {productId}");
        Driver.Navigate().GoToUrl($"{Settings.BaseUrl}/products/{productId}");
        WaitForPageLoad();
        return this;
    }

    public string GetProductTitle()
    {
        var locator = base.Locators != null 
            ? GetLocator("ProductTitle") 
            : Locators.ProductTitle;
        return GetText(locator);
    }

    public CartPage AddToCart()
    {
        Logger.Step("Adding product to cart");
        var locator = base.Locators != null 
            ? GetLocator("AddToCartButton") 
            : Locators.AddToCartButton;
        Click(locator);
        return new CartPage();
    }

    public decimal GetPrice()
    {
        var locator = base.Locators != null 
            ? GetLocator("PriceLabel") 
            : Locators.PriceLabel;
        var priceText = GetText(locator);
        return decimal.Parse(priceText.Replace("$", ""));
    }
}

BasePage Methods

Method Description
FindElement(By) Find element with wait
FindElements(By) Find multiple elements
Click(By) Click element
Type(By, string) Type text into element
GetText(By) Get element text
IsElementDisplayed(By) Check if element visible
WaitForElementVisible(By) Wait for element to be visible
WaitForElementClickable(By) Wait for element to be clickable
SelectByText(By, string) Select dropdown option
Hover(By) Hover over element
ScrollIntoView(By) Scroll element into view

🎯 Locator Management

Locator JSON Format

The framework uses a simplified one-line format for easy maintenance:

{
  "PageName": "LoginPage",
  "Description": "Login page locators",
  "Elements": {
    "UsernameInput": "Id:username",
    "PasswordInput": "Id:password",
    "LoginButton": "CssSelector:button[type='submit']",
    "ErrorMessage": "CssSelector:.error-message",
    "ForgotPasswordLink": "LinkText:Forgot Password?",
    "RememberMeCheckbox": "Id:remember-me"
  }
}

Format: "ElementName": "Type:Value"

Locator Types

Type Format Example
Id "Id:username"
Name "Name:email"
ClassName "ClassName:btn-primary"
CssSelector "CssSelector:button.submit"
XPath "XPath://button[@type='submit']"
LinkText "LinkText:Sign In"
PartialLinkText "PartialLinkText:Sign"
TagName "TagName:button"

Dynamic Locators

Use format placeholders {0}, {1}, etc. for dynamic values:

{
  "PageName": "ProductPage",
  "Elements": {
    "ProductById": "XPath://div[@data-product-id='{0}']",
    "CategoryItem": "CssSelector:[data-category='{0}'] .item:nth-child({1})"
  }
}
// Usage in Page Object
var locator = GetLocator("ProductById", productId);
Click(locator);

// Multiple parameters
var locator = GetLocator("CategoryItem", "electronics", 3);

Locator Best Practices

  1. Prefer stable attributes: id, data-testid, name
  2. Avoid brittle locators: Position-based XPath, generated classes
  3. Use CSS over XPath: Generally faster and more readable
  4. Keep locators short: Avoid long chains
  5. Use simplified format: One line per element for easy editing

πŸƒ Running Tests

Run All Tests

dotnet test

Run with Specific Browser

TEST_AUTO_BROWSER=Firefox dotnet test

Run in Headless Mode

TEST_AUTO_HEADLESS=true dotnet test

Run Specific Category

dotnet test --filter "Category=Smoke"
dotnet test --filter "Category=Regression"

Run Specific Test

dotnet test --filter "FullyQualifiedName~LoginTests"
dotnet test --filter "Name=VerifyHomePageLoads"

Run with Verbosity

dotnet test --verbosity normal
dotnet test --verbosity detailed

Run Against Specific Environment

TEST_ENVIRONMENT=Staging dotnet test

Parallel Execution

Tests marked with [Parallelizable] run in parallel:

dotnet test -- NUnit.NumberOfTestWorkers=4

πŸ“Š Reporting

Extent Reports

HTML reports are generated automatically in the Reports folder.

Report Features:

  • Test execution summary
  • Pass/Fail/Skip statistics
  • Screenshots on failure
  • Step-by-step execution logs
  • System information
  • Timeline view

Viewing Reports

After test execution, report will be created at location : Reports :

Log Files

Logs are stored in the Logs folder with timestamps.


πŸ”Œ API Testing

The framework includes a powerful REST API testing capability built on RestSharp, enabling hybrid UI + API testing.

API Client Features

  • Full HTTP Support - GET, POST, PUT, PATCH, DELETE
  • Authentication - Bearer Token, Basic Auth, API Key
  • Typed Responses - Automatic JSON deserialization
  • Fluent Assertions - Chain assertions on responses
  • Async/Sync - Both async and synchronous methods
  • File Upload - Multipart form data support
  • Request Logging - Automatic logging of requests/responses

Basic API Usage

using TestAutomation.Framework.Api;

// Create API client
var apiClient = new ApiClient("https://api.example.com");

// GET request with typed response
var response = apiClient.Get<List<User>>("/users");
response.ShouldBeSuccessful();
response.Data.Should().NotBeEmpty();

// POST request
var newUser = new { name = "John", email = "john@example.com" };
var createResponse = apiClient.Post<User>("/users", newUser);
createResponse.ShouldBeCreated();

// With authentication
apiClient.WithBearerToken("your-token");
var protectedResponse = apiClient.Get<Profile>("/profile");

Authentication Methods

// Bearer Token
var client = new ApiClient("https://api.example.com")
    .WithBearerToken("eyJhbGciOiJIUzI1NiIs...");

// Basic Auth
var client = new ApiClient("https://api.example.com")
    .WithBasicAuth("username", "password");

// API Key
var client = new ApiClient("https://api.example.com")
    .WithApiKey("your-api-key", "X-API-Key");

// Custom Headers
var client = new ApiClient("https://api.example.com")
    .WithHeader("X-Custom-Header", "value");

API Assertions

// Status code assertions
response.ShouldBeOk();           // 200
response.ShouldBeCreated();      // 201
response.ShouldBeNoContent();    // 204
response.ShouldBeBadRequest();   // 400
response.ShouldBeUnauthorized(); // 401
response.ShouldBeForbidden();    // 403
response.ShouldBeNotFound();     // 404

// Custom status code
response.ShouldHaveStatusCode(HttpStatusCode.Accepted);

// Content assertions
response.ShouldBeSuccessful();
response.ShouldHaveData();
response.ShouldContain("expected text");

// Header assertions
response.ShouldHaveHeader("Content-Type");
response.ShouldHaveHeader("X-Request-Id", "12345");

// Performance assertions
response.ShouldCompleteWithin(5000); // 5 seconds max

Hybrid Testing (API + UI)

Combine API and UI testing for faster, more reliable tests:

[Test]
public void CreateDataViaApi_VerifyInUI()
{
    // STEP 1: Create test data via API (fast)
    var apiClient = new ApiClient("https://api.example.com");
    var response = apiClient.Post<Order>("/orders", new { 
        product = "Widget", 
        quantity = 5 
    });
    response.ShouldBeCreated();
    var orderId = response.Data!.Id;

    // STEP 2: Verify in UI
    NavigateToBaseUrl();
    var orderPage = new OrderPage();
    orderPage.NavigateTo(orderId);
    orderPage.GetStatus().Should().Be("Created");
}

[Test]
public void LoginViaApi_InjectTokenToBrowser()
{
    // Login via API (faster than UI)
    var authClient = new ApiClient("https://api.example.com");
    var loginResponse = authClient.Post<LoginResponse>("/auth/login", new {
        username = "testuser",
        password = "testpass"
    });
    var token = loginResponse.Data!.Token;

    // Inject token into browser
    NavigateToBaseUrl();
    ((IJavaScriptExecutor)Driver).ExecuteScript(
        $"localStorage.setItem('token', '{token}');");
    Driver.Navigate().Refresh();

    // Verify logged in state
    var homePage = new HomePage();
    homePage.IsUserLoggedIn().Should().BeTrue();
}

Test Organization

tests/TestAutomation.Tests/
β”œβ”€β”€ Tests/
β”‚   β”œβ”€β”€ API/                 # Pure API tests
β”‚   β”‚   β”œβ”€β”€ SampleApiTests.cs
β”‚   β”‚   └── AuthApiTests.cs
β”‚   β”œβ”€β”€ UI/                  # Pure UI tests
β”‚   β”‚   β”œβ”€β”€ LoginTests.cs
β”‚   β”‚   └── SampleTests.cs
β”‚   └── Hybrid/              # Combined API + UI tests
β”‚       └── HybridTestExample.cs

Running API Tests Only

# Run only API tests
dotnet test --filter "Category=API"

# Run only UI tests
dotnet test --filter "Category=UI"

# Run hybrid tests
dotnet test --filter "Category=Hybrid"

πŸ”„ CI/CD Integration

GitHub Actions

The framework includes pre-configured GitHub Actions workflows:

Main Workflow (.github/workflows/test.yml)

  • Triggers on push/PR to main/develop
  • Supports manual trigger with environment selection
  • Multi-browser matrix testing
  • Uploads test artifacts

Scheduled Tests (.github/workflows/scheduled-tests.yml)

  • Runs daily at 2 AM UTC
  • Executes regression test suite
  • Multi-browser testing

GitHub Secrets

Configure these secrets in your repository:

Secret Description
BASE_URL Application base URL

Jenkins

Use the included Jenkinsfile:

// Trigger build with parameters
// - ENVIRONMENT: Development/Staging/Production
// - BROWSER: Chrome/Firefox/Edge
// - HEADLESS: true/false
// - TEST_FILTER: NUnit filter expression

Docker

# Example Dockerfile for containerized execution
FROM mcr.microsoft.com/dotnet/sdk:10.0

# Install Chrome
RUN apt-get update && apt-get install -y chromium

WORKDIR /app
COPY . .
RUN dotnet restore
RUN dotnet build

CMD ["dotnet", "test"]

🌐 Selenium Grid

The framework supports Selenium Grid for distributed test execution across multiple browsers and machines.

What is Selenium Grid?

Selenium Grid allows you to:

  • Run tests on multiple browsers simultaneously
  • Execute tests on remote machines
  • Scale test execution horizontally
  • Test on different browser versions

Quick Start with Docker Compose

A docker-compose.yml is included for easy Grid setup:

# Start Selenium Grid (Hub + Chrome, Firefox, Edge nodes)
docker-compose up -d

# Verify Grid is running
# Open browser: http://localhost:4444/ui

# Run tests against Grid
TEST_AUTO_USE_REMOTE_DRIVER=true \
TEST_AUTO_REMOTE_WEBDRIVER_URL=http://localhost:4444/wd/hub \
dotnet test

# Stop Grid
docker-compose down

Grid Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                     Selenium Grid Hub                        β”‚
β”‚                   http://localhost:4444                      β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                                              β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”         β”‚
β”‚  β”‚   Chrome    β”‚  β”‚   Firefox   β”‚  β”‚    Edge     β”‚         β”‚
β”‚  β”‚    Node     β”‚  β”‚    Node     β”‚  β”‚    Node     β”‚         β”‚
β”‚  β”‚  (4 slots)  β”‚  β”‚  (4 slots)  β”‚  β”‚  (4 slots)  β”‚         β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜         β”‚
β”‚                                                              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Configuration Options

Option 1: Environment Variables

export TEST_AUTO_USE_REMOTE_DRIVER=true
export TEST_AUTO_REMOTE_WEBDRIVER_URL=http://localhost:4444/wd/hub
export TEST_AUTO_BROWSER=Chrome
dotnet test

Option 2: appsettings.json

{
  "TestSettings": {
    "UseRemoteDriver": true,
    "RemoteWebDriverUrl": "http://localhost:4444/wd/hub",
    "Browser": "Chrome"
  }
}

Option 3: Environment-specific config (appsettings.Staging.json)

{
  "TestSettings": {
    "UseRemoteDriver": true,
    "RemoteWebDriverUrl": "http://selenium-grid.company.com:4444/wd/hub"
  }
}

Standalone Browser (Single Node)

For simpler setups, use standalone containers:

# Chrome only
docker run -d -p 4444:4444 --shm-size="2g" selenium/standalone-chrome:4.25.0

# Firefox only
docker run -d -p 4444:4444 --shm-size="2g" selenium/standalone-firefox:4.25.0

# Edge only
docker run -d -p 4444:4444 --shm-size="2g" selenium/standalone-edge:4.25.0

Cloud Selenium Grid Providers

The framework also works with cloud providers:

Provider Remote URL Format
BrowserStack https://USER:KEY@hub-cloud.browserstack.com/wd/hub
Sauce Labs https://USER:KEY@ondemand.saucelabs.com/wd/hub
LambdaTest https://USER:KEY@hub.lambdatest.com/wd/hub
# Example with BrowserStack
export TEST_AUTO_USE_REMOTE_DRIVER=true
export TEST_AUTO_REMOTE_WEBDRIVER_URL="https://user:key@hub-cloud.browserstack.com/wd/hub"
dotnet test

Grid in CI/CD (GitHub Actions)

services:
  selenium:
    image: selenium/standalone-chrome:4.25.0
    ports:
      - 4444:4444
    options: --shm-size="2g"

steps:
  - name: Run tests on Grid
    run: dotnet test
    env:
      TEST_AUTO_USE_REMOTE_DRIVER: true
      TEST_AUTO_REMOTE_WEBDRIVER_URL: http://localhost:4444/wd/hub

Scaling the Grid

Increase browser nodes for more parallel capacity:

# Scale Chrome nodes to 5 instances
docker-compose up -d --scale chrome=5

# Scale all browsers
docker-compose up -d --scale chrome=3 --scale firefox=3 --scale edge=2

πŸ€– MCP Integration

The framework is designed for future MCP (Model Context Protocol) integration to enable AI-assisted testing.

Planned Features

  1. Test Context Sharing - Share execution state with AI
  2. Locator Healing - AI-powered locator repair
  3. Failure Analysis - Automatic root cause analysis
  4. Test Generation - Generate tests from descriptions

See src/TestAutomation.Framework/MCP/McpIntegrationReadme.md for details.


πŸ“š Best Practices

Test Design

  • βœ… One assertion focus per test
  • βœ… Independent tests (no dependencies)
  • βœ… Meaningful test names
  • βœ… Proper test categorization
  • βœ… Clean up test data

Page Objects

  • βœ… Single Responsibility Principle
  • βœ… Fluent method chaining
  • βœ… No assertions in page objects
  • βœ… Reusable components

Locators

  • βœ… Use data-testid attributes
  • βœ… Externalize in JSON files
  • βœ… Avoid brittle locators
  • βœ… Document complex locators

Waits

  • βœ… Use explicit waits
  • βœ… Avoid Thread.Sleep
  • βœ… Wait for specific conditions
  • βœ… Set reasonable timeouts

Configuration

  • βœ… No hardcoded values
  • βœ… Environment-specific configs
  • βœ… Secrets in environment variables
  • βœ… Sensible defaults

πŸ”§ Troubleshooting

Common Issues

Driver not found

WebDriverException: Cannot find Chrome binary

Solution: Install Chrome or set TEST_AUTO_BROWSER to an installed browser.

Element not found

NoSuchElementException: Unable to locate element

Solution:

  • Verify locator is correct
  • Add explicit wait
  • Check if element is in iframe

Timeout exceptions

WebDriverTimeoutException: Timed out after X seconds

Solution:

  • Increase timeout in settings
  • Check network connectivity
  • Verify page loads correctly

Headless mode issues

Tests fail in headless but pass in headed mode

Solution:

  • Set window size explicitly
  • Check for viewport-dependent elements
  • Review console errors

Debug Mode

Enable detailed logging:

{
  "TestSettings": {
    "EnableDetailedLogging": true
  }
}

Getting Help

  1. Check the logs in Logs/ folder
  2. Review screenshots in Screenshots/ folder
  3. Check the Extent Report for details
  4. Enable verbose test output: dotnet test -v d

🀝 Contributing

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature/my-feature
  3. Commit changes: git commit -am 'Add my feature'
  4. Push to branch: git push origin feature/my-feature
  5. Submit a Pull Request

Code Style

  • Follow C# naming conventions
  • Add XML documentation comments
  • Write unit tests for utilities
  • Update README for new features

πŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.


πŸ“ž Support


Happy Testing! πŸš€

About

πŸš€ A robust, maintainable C# Selenium automation framework using NUnit, designed for efficient functional and regression testing with built-in reporting and logging.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages