QA Engineering Assessment · Player API

Player API
Tests

ASP.NET Core 8 Web API built and tested solo in 3 days. Full NUnit suite covering unit and integration layers — 28 tests, all green.

ASP.NET Core 8 · C# 12 · NUnit 3 · WebApplicationFactory · Swagger · Railway

☁️ Live Swagger </> GitHub ⚡ CI Pipeline
✓ 28 Tests Pass ☁️ Live on Railway 🔄 CI/CD Green 5 API Endpoints 12 Unit + 16 Integration 3-Day Sprint AI-First Delivery
</>

Source Code

Full solution: ASP.NET Core API project, NUnit test project, GitHub Actions CI/CD, all documentation in /docs.

Public · C# 12 · .NET 8 View Repository →
⚡

CI Pipeline

GitHub Actions: dotnet restore → build → test → TRX report → HTML report published to GitHub Pages.

ubuntu-latest · .NET 8 · NUnit3 View Pipeline →
☁️

Live API & Swagger

Fully deployed on Railway. Interactive Swagger UI lets you explore and call all 5 endpoints without any setup.

Railway · ASP.NET Core 8 · Swashbuckle Open Swagger UI → Free tier — first request after inactivity may take ~5s

About This Project

The Challenge

A QA Engineering Assessment requiring candidates to design and implement a production-ready REST API for player management from scratch — then write comprehensive test coverage for it.

The constraint: 3-day sprint, solo delivery, acting simultaneously as API developer, QA engineer, and delivery manager.

This project demonstrates that an experienced QA Engineer can own both the implementation and the verification — not just test what others build.

The Approach

AI-First Engineering: Claude Code was used as the primary accelerator — not a replacement for engineering judgment. Every decision is documented in architectural records and a specification file that served as the project's source of truth.

Two-layer test strategy:

  • 12 unit tests — PlayerStore in isolation, no HTTP
  • 16 integration tests — full API pipeline via WebApplicationFactory
  • 100% endpoint coverage, positive and negative paths
  • All 28 tests green on clean clone

Delivered on time with full documentation and live CI pipeline.

Project Documentation Library

Engineering artefacts authored during the sprint — architectural decisions, test plan, and security assessment.

Architecture Decisions
ADR-001
In-Memory Storage
Why ConcurrentDictionary was chosen over SQLite or Entity Framework. Zero external dependencies, deterministic test resets, thread-safe by design.
View → ADR-002
WebApplicationFactory for Testing
Why in-process integration testing was chosen over a real HTTP server. Full pipeline coverage without ports, deployment, or network overhead.
View → ADR-003
Stateless JWT Authentication
Why stateless JWT with 1-hour expiry was chosen. No refresh tokens, no claims, no sessions — signature validation is sufficient for assessment scope.
View →
Quality Engineering
TEST-PLAN
Test Plan
Two-layer test strategy, coverage goals, data model under test, isolation strategy, full unit and integration test matrices. 28 tests mapped to requirements.
View →
Security
SECURITY
OWASP API Security Assessment
OWASP API Security Top 10 relevance table covering auth, object-level access, misconfiguration, and inventory management. Explicit scope exclusions documented.
View →

Tech Stack

Every tool selected for a documented reason — see the ADR collection for full justification.

⚙️
ASP.NET Core 8
LTS Web API framework — minimal hosting model, built-in DI
🔮
C# 12
Primary constructors, records, pattern matching — clean models
🧰
NUnit 3
Unit + integration test framework — rich assertion model
🔌
WebApplicationFactory
In-process integration testing — no real ports, no deployment
🔒
JWT Bearer
Stateless auth — signature-only validation, 1-hour expiry
🚫
ConcurrentDictionary
Thread-safe in-memory store — zero I/O, deterministic resets
📄
Swagger (Swashbuckle)
Auto-generated API docs from XML comments — zero extra cost
⚡
GitHub Actions
Build → Test → TRX report → HTML report → Railway deploy
🚂
Railway
Free-tier Docker deployment — public API URL + Swagger UI
🤖
Claude Code
AI engineering accelerator — primary development tool
Evgenii Subbotin
QA/SDET Lead · QA Architect · SAFe RTE

20 years in software engineering. This project demonstrates full-cycle API delivery — design, implementation, testing, documentation, and CI/CD in a 3-day solo sprint.

LinkedIn GitHub Email All Projects