Add E2E.Tests Aspire xUnit project by mpaulosky · Pull Request #49 · mpaulosky/MyBlog

mpaulosky · 2026-04-19T19:43:00Z

Summary

Adds tests/E2E.Tests — an Aspire xUnit project that spins up the full application via DistributedApplicationTestingBuilder and validates HTTP-level behavior.

Closes #48

Working as Pippin (test specialist)

Changes

File	Action
`tests/E2E.Tests/E2E.Tests.csproj`	Created — `net10.0` xUnit project referencing AppHost
`tests/E2E.Tests/GlobalUsings.cs`	Created — standard header + global usings
`tests/E2E.Tests/xunit.runner.json`	Created — `parallelizeAssembly=false`
`tests/E2E.Tests/WebAppTests.cs`	Created — smoke test: `GET /` → `200 OK`
`MyBlog.slnx`	Updated — E2E.Tests added under `/tests/` folder

Testing

Smoke test uses DistributedApplicationTestingBuilder<Projects.MyBlog_AppHost> to start the full Aspire stack
Waits for webfrontend resource healthy (60s timeout)
Asserts GET / returns 200 OK
No Testcontainers needed — Aspire manages MongoDB + Redis infra

Process Note

⚠️ This task was flagged as "needs review" — initial implementation bypassed the plan workflow (no issue/branch/project tracking). Remediated: issue #48 created, added to Project #4, work moved to proper squad/48-add-e2e-tests branch.

Closes #48 - Add tests/E2E.Tests/E2E.Tests.csproj (net10.0, Aspire xUnit) - Add tests/E2E.Tests/GlobalUsings.cs with standard header - Add tests/E2E.Tests/xunit.runner.json (parallelizeAssembly=false) - Add tests/E2E.Tests/WebAppTests.cs (smoke test: GET / -> 200 OK) - Update MyBlog.slnx to include E2E.Tests under /tests/ folder Working as Pippin (test specialist) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

github-actions · 2026-04-19T19:44:08Z

Summary


Generated on:	04/19/2026 - 19:44:08
Coverage date:	04/19/2026 - 19:43:47 - 04/19/2026 - 19:43:55
Parser:	MultiReport (4x Cobertura)
Assemblies:	4
Classes:	35
Files:	34
Line coverage:	64.3% (474 of 737)
Covered lines:	474
Uncovered lines:	263
Coverable lines:	737
Total lines:	2069
Branch coverage:	64% (169 of 264)
Covered branches:	169
Total branches:	264
Method coverage:	Feature is only available for sponsors
Tag:	55_24637522862

Coverage

AppHost - 0%

Name	Line	Branch
AppHost	0%	****
Program	0%

Domain - 93.4%

Name	Line	Branch
Domain	93.4%	50%
Domain.Abstractions.Result	95%	50%
Domain.Abstractions.Result`1	75%	50%
MyBlog.Domain.Entities.BlogPost	100%

ServiceDefaults - 0%

Name	Line	Branch
ServiceDefaults	0%	0%
Microsoft.Extensions.Hosting.Extensions	0%	0%

Web - 68.1%

Name	Line	Branch
Web	68.1%	69%
MyBlog.Web.Components.Layout.MainLayout	100%
MyBlog.Web.Components.Layout.NavMenu	82.8%	71.4%
MyBlog.Web.Components.Pages.Error	100%	75%
MyBlog.Web.Components.Routes	0%	0%
MyBlog.Web.Components.Shared.RedirectToLogin	100%
MyBlog.Web.Data.BlogDbContext	100%
MyBlog.Web.Data.BlogPostDto	100%
MyBlog.Web.Data.BlogPostMappings	100%
MyBlog.Web.Data.MongoDbBlogPostRepository	100%	100%
MyBlog.Web.Features.BlogPosts.Create.Create	75%	50%
MyBlog.Web.Features.BlogPosts.Create.CreateBlogPostCommand	100%
MyBlog.Web.Features.BlogPosts.Create.CreateBlogPostHandler	100%
MyBlog.Web.Features.BlogPosts.Delete.ConfirmDeleteDialog	100%	100%
MyBlog.Web.Features.BlogPosts.Delete.DeleteBlogPostCommand	100%
MyBlog.Web.Features.BlogPosts.Delete.DeleteBlogPostHandler	100%
MyBlog.Web.Features.BlogPosts.Edit.Edit	88%	75%
MyBlog.Web.Features.BlogPosts.Edit.EditBlogPostCommand	100%
MyBlog.Web.Features.BlogPosts.Edit.EditBlogPostHandler	84%	90%
MyBlog.Web.Features.BlogPosts.Edit.GetBlogPostByIdQuery	100%
MyBlog.Web.Features.BlogPosts.List.GetBlogPostsHandler	100%	100%
MyBlog.Web.Features.BlogPosts.List.Index	86.8%	84.6%
MyBlog.Web.Features.UserManagement.AssignRoleCommand	100%
MyBlog.Web.Features.UserManagement.ManageRoles	90.4%	75%
MyBlog.Web.Features.UserManagement.Profile	97.2%	82%
MyBlog.Web.Features.UserManagement.RemoveRoleCommand	100%
MyBlog.Web.Features.UserManagement.RoleDto	100%
MyBlog.Web.Features.UserManagement.UserManagementHandler	0%	0%
MyBlog.Web.Features.UserManagement.UserWithRolesDto	100%
MyBlog.Web.Security.RoleClaimsHelper	91.8%	91.1%
Program	0%	0%

Copilot

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new end-to-end (E2E) xUnit test project that boots the full Aspire distributed application and validates basic HTTP behavior, and wires it into the solution.

Changes:

Added tests/E2E.Tests xUnit project referencing the AppHost and configuring xUnit runner settings.
Implemented an initial smoke test that starts the Aspire stack and asserts GET / returns 200 OK.
Updated the solution (MyBlog.slnx) to include the new E2E test project.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
tests/E2E.Tests/E2E.Tests.csproj	New E2E test project targeting a new TFM with test/Aspire dependencies and AppHost reference
tests/E2E.Tests/GlobalUsings.cs	Global usings for Aspire testing, xUnit, and FluentAssertions
tests/E2E.Tests/xunit.runner.json	xUnit runner configuration to control parallelization and display options
tests/E2E.Tests/WebAppTests.cs	Smoke test that boots the distributed app and checks `/` returns 200
MyBlog.slnx	Adds E2E.Tests project under the `/tests/` solution folder

Copilot · 2026-04-19T19:44:50Z

+  "methodDisplay": "method",
+  "methodDisplayOptions": "all",
+  "parallelizeAssembly": false,
+  "parallelizeTestCollections": true


parallelizeTestCollections is effectively moot when parallelizeAssembly is false, which can be confusing for future test additions. Consider setting both to false for clarity, or enable assembly parallelization if you truly want collections to run concurrently.

Suggested change

"parallelizeTestCollections": true

"parallelizeTestCollections": false

Copilot · 2026-04-19T19:44:51Z

+
+public class WebAppTests
+{
+    private static readonly TimeSpan DefaultTimeout = TimeSpan.FromSeconds(60);


Timeout handling is currently duplicated: a 60s CancellationTokenSource governs the entire test, and then each step also adds a separate WaitAsync(DefaultTimeout, cancellationToken). This makes it harder to reason about total time budget and failure modes (cancellation vs timeout exceptions). Consider either (a) using the CTS token only (no WaitAsync(timeout)), or (b) using step-specific timeouts without a global 60s CTS (or a larger global CTS plus smaller per-step timeouts).

Copilot · 2026-04-19T19:44:51Z

+    public async Task GetWebResourceRootReturnsOkStatusCode()
+    {
+        // Arrange
+        var cancellationToken = new CancellationTokenSource(DefaultTimeout).Token;


Timeout handling is currently duplicated: a 60s CancellationTokenSource governs the entire test, and then each step also adds a separate WaitAsync(DefaultTimeout, cancellationToken). This makes it harder to reason about total time budget and failure modes (cancellation vs timeout exceptions). Consider either (a) using the CTS token only (no WaitAsync(timeout)), or (b) using step-specific timeouts without a global 60s CTS (or a larger global CTS plus smaller per-step timeouts).

Copilot · 2026-04-19T19:44:51Z

+        await using var app = await appHost.BuildAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);
+        await app.StartAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);
+
+        // Act
+        using var httpClient = app.CreateHttpClient("webfrontend");
+        await app.ResourceNotifications
+            .WaitForResourceHealthyAsync("webfrontend", cancellationToken)
+            .WaitAsync(DefaultTimeout, cancellationToken);


Timeout handling is currently duplicated: a 60s CancellationTokenSource governs the entire test, and then each step also adds a separate WaitAsync(DefaultTimeout, cancellationToken). This makes it harder to reason about total time budget and failure modes (cancellation vs timeout exceptions). Consider either (a) using the CTS token only (no WaitAsync(timeout)), or (b) using step-specific timeouts without a global 60s CTS (or a larger global CTS plus smaller per-step timeouts).

Suggested change

await using var app = await appHost.BuildAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);

await app.StartAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);

// Act

using var httpClient = app.CreateHttpClient("webfrontend");

await app.ResourceNotifications

.WaitForResourceHealthyAsync("webfrontend", cancellationToken)

.WaitAsync(DefaultTimeout, cancellationToken);

await using var app = await appHost.BuildAsync(cancellationToken);

await app.StartAsync(cancellationToken);

// Act

using var httpClient = app.CreateHttpClient("webfrontend");

await app.ResourceNotifications

.WaitForResourceHealthyAsync("webfrontend", cancellationToken);

Copilot · 2026-04-19T19:44:52Z

+        await using var app = await appHost.BuildAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);
+        await app.StartAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);
+
+        // Act
+        using var httpClient = app.CreateHttpClient("webfrontend");
+        await app.ResourceNotifications
+            .WaitForResourceHealthyAsync("webfrontend", cancellationToken)
+            .WaitAsync(DefaultTimeout, cancellationToken);


Timeout handling is currently duplicated: a 60s CancellationTokenSource governs the entire test, and then each step also adds a separate WaitAsync(DefaultTimeout, cancellationToken). This makes it harder to reason about total time budget and failure modes (cancellation vs timeout exceptions). Consider either (a) using the CTS token only (no WaitAsync(timeout)), or (b) using step-specific timeouts without a global 60s CTS (or a larger global CTS plus smaller per-step timeouts).

Suggested change

await using var app = await appHost.BuildAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);

await app.StartAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken);

// Act

using var httpClient = app.CreateHttpClient("webfrontend");

await app.ResourceNotifications

.WaitForResourceHealthyAsync("webfrontend", cancellationToken)

.WaitAsync(DefaultTimeout, cancellationToken);

await using var app = await appHost.BuildAsync(cancellationToken);

await app.StartAsync(cancellationToken);

// Act

using var httpClient = app.CreateHttpClient("webfrontend");

await app.ResourceNotifications

.WaitForResourceHealthyAsync("webfrontend", cancellationToken);

Copilot · 2026-04-19T19:44:52Z

+        appHost.Services.ConfigureHttpClientDefaults(clientBuilder =>
+        {
+            clientBuilder.AddStandardResilienceHandler();
+        });
+


AddStandardResilienceHandler() typically enables retries/backoff policies, which can make E2E failures slower and sometimes less deterministic (a failing endpoint may take longer to surface). For a smoke test, consider configuring a minimal/no-retry policy (or a test-specific resilience configuration) so failures are reported quickly and consistently.

Suggested change

appHost.Services.ConfigureHttpClientDefaults(clientBuilder =>

{

clientBuilder.AddStandardResilienceHandler();

});

Copilot AI review requested due to automatic review settings April 19, 2026 19:43

Copilot started reviewing on behalf of mpaulosky April 19, 2026 19:43 View session

Copilot AI reviewed Apr 19, 2026

View reviewed changes

mpaulosky closed this Apr 19, 2026

mpaulosky deleted the squad/48-add-e2e-tests branch April 19, 2026 20:42

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add E2E.Tests Aspire xUnit project#49

Add E2E.Tests Aspire xUnit project#49
mpaulosky wants to merge 1 commit into
devfrom
squad/48-add-e2e-tests

mpaulosky commented Apr 19, 2026

Uh oh!

github-actions Bot commented Apr 19, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 19, 2026

Uh oh!

Copilot AI Apr 19, 2026

Uh oh!

Copilot AI Apr 19, 2026

Uh oh!

Copilot AI Apr 19, 2026

Uh oh!

Copilot AI Apr 19, 2026

Uh oh!

Copilot AI Apr 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	"parallelizeTestCollections": true
	"parallelizeTestCollections": false

Conversation

mpaulosky commented Apr 19, 2026

Summary

Changes

Testing

Process Note

Uh oh!

github-actions Bot commented Apr 19, 2026

Summary

Coverage

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants