Testing, debugging, and performance

What this bullet means

The employer wants evidence that you can find bugs, verify behavior, and pay attention to performance instead of only making screens that look finished.

Sample app idea

Route Exception Processing Dashboard that imports sample route events and flags late, duplicate, or missing status updates.

Main build outline

1. Create an import routine for sample transportation event records.
2. Add validation rules that detect duplicate route events, missing timestamps, and invalid statuses.
3. Write focused unit tests for the validation service.
4. Add logging around import results and failed records.
5. Add a simple summary page showing processed, rejected, and warning counts.

Portfolio proof

• Test results screenshot.
• README debugging notes with two example defects and fixes.
• Before-and-after explanation for one performance or query improvement.
• Sample data file with no private information.

Minimal documentation

• README with the business problem, screenshots, setup notes, and technology stack.
• One requirements note that maps the job bullet to the sample feature.
• One test plan note with happy path, validation, and edge case checks.
• One honest portfolio note that says this is self-directed practice, not employer work.

Modern .NET stack

• Blazor Server or ASP.NET Core Razor Pages.
• C# services with validation and dependency injection.
• SQL Server locally, then SmarterASP SQL Server or Azure SQL.
• Optional Azure App Service, GitHub Actions, Docker, and AI helper feature.