GuyStore — Testing Guide

This guide covers how to run, understand, and extend the three-layer test suite for the GuyStore ASP.NET Core 9 e-commerce platform.

Overview

Prerequisites

• .NET 9 SDK — required for all three projects.
• Playwright browsers — required for E2E only; install once with the command below.

No external services are needed. All tests use an in-memory EF Core database, no-op SMTP, and simulation-mode translation.

Running All Tests

From the solution root (the folder containing GuyStore.sln):

dotnet test

Unit Tests Only

dotnet test GuyStore.Tests.Unit/GuyStore.Tests.Unit.csproj

Integration Tests Only

dotnet test GuyStore.Tests.Integration/GuyStore.Tests.Integration.csproj

E2E Tests

Step 1 — Install Playwright browsers (one-time)

cd GuyStore.Tests.E2E
dotnet build
pwsh bin/Debug/net9.0/playwright.ps1 install chromium

Step 2 — Run

dotnet test GuyStore.Tests.E2E/GuyStore.Tests.E2E.csproj

Useful filters

# Run tests matching a class name
dotnet test --filter "FullyQualifiedName~ReviewControllerTests"

# Run tests matching a method name
dotnet test --filter "FullyQualifiedName~Submit_AuthenticatedUser"

# Skip E2E (unit + integration only)
dotnet test --filter "FullyQualifiedName!~GuyStore.Tests.E2E"

# Verbose output
dotnet test --logger "console;verbosity=detailed"

Unit Test Structure

Pure in-process tests — no network, no database, no file system. Dependencies are replaced with Moq mocks or lightweight fakes.

Integration Test Structure

Tests send real HTTP requests through the ASP.NET Core pipeline. Each test class gets its own WebApplicationFactory instance with a fresh in-memory database, automatically seeded by DataSeeder.

Helpers

Controller Coverage

E2E Test Structure

All E2E test classes share a single PlaywrightFixture via [Collection("E2E")]. The fixture starts a Kestrel server, seeds data, and opens a headless Chromium browser. Each test method opens its own page and closes it when done.

Seeded Test Data

Every test database is pre-populated by DataSeeder.SeedAsync():

Test Isolation

Continuous Integration

GitHub Actions example

- name: Install Playwright browsers
  run: |
    cd GuyStore.Tests.E2E
    dotnet build --configuration Release
    pwsh bin/Release/net9.0/playwright.ps1 install chromium --with-deps

- name: Run unit + integration tests
  run: dotnet test --filter "FullyQualifiedName!~GuyStore.Tests.E2E" --configuration Release

- name: Run E2E tests
  run: dotnet test GuyStore.Tests.E2E --configuration Release

Adding New Tests

New unit test

// Example
public class MyModelTests
{
    [Fact]
    public void Property_CanBeSet() { ... }

    [Theory]
    [InlineData(1, true)]
    [InlineData(0, false)]
    public void Condition_ReturnsExpected(int value, bool expected) { ... }
}

New integration test

public class MyControllerTests : IClassFixture<GuyStoreWebApplicationFactory>
{
    private readonly GuyStoreWebApplicationFactory _factory;
    public MyControllerTests(GuyStoreWebApplicationFactory factory) => _factory = factory;

    private HttpClient FreshClient() =>
        _factory.CreateClient(new WebApplicationFactoryClientOptions { AllowAutoRedirect = true });

    [Fact]
    public async Task SomeAction_Returns200()
    {
        var client = FreshClient();
        await client.LoginAsync("[email protected]", "Admin@123");
        var response = await client.GetAsync("/SomeController/SomeAction");
        response.EnsureSuccessStatusCode();
    }
}

New E2E test

[Collection("E2E")]
public class MyFeatureTests
{
    private readonly PlaywrightFixture _fixture;
    public MyFeatureTests(PlaywrightFixture fixture) => _fixture = fixture;

    [Fact]
    public async Task FeaturePage_IsAccessible()
    {
        var page = await _fixture.NewPageAsync();
        await LoginAsAdminAsync(page);
        await page.GotoAsync($"{_fixture.BaseUrl}/MyFeature");
        await page.WaitForLoadStateAsync(LoadState.NetworkIdle);

        var html = await page.ContentAsync();
        Assert.Contains("My Feature", html);
        await page.CloseAsync();
    }

    private async Task LoginAsAdminAsync(IPage page)
    {
        await page.GotoAsync($"{_fixture.BaseUrl}/Account/Login");
        await page.WaitForLoadStateAsync(LoadState.NetworkIdle);
        await page.FillAsync("input[name='Email']", "[email protected]");
        await page.FillAsync("input[name='Password']", "Admin@123");
        await page.RunAndWaitForNavigationAsync(
            () => page.ClickAsync("button[type='submit']"),
            new PageRunAndWaitForNavigationOptions { WaitUntil = WaitUntilState.NetworkIdle });
    }
}

Testing Passkey / WebAuthn endpoints

The BeginRegistration and BeginAuthentication endpoints are testable with a standard HttpClient — they just return JSON and write to session. Use an integration test that calls GET /Passkey/BeginRegistration (authenticated) and asserts the response contains challenge and rp fields.

CompleteRegistration and CompleteAuthentication require a real WebAuthn authenticator response, which can only be produced by a browser. Use Playwright's virtual authenticator API (page.AddVirtualAuthenticatorAsync()) in an E2E test to create and assert a full passkey registration → sign-in flow without real biometrics.