AgrarianGameArchive/Docs/QA/MvpQaGates.md

MVP QA Gates

Version 0.1.Q turns the current survival MVP into a repeatable test target. Each gate must have either automation, a documented manual test, or build evidence before it is marked complete.

Packaged Client Launch

The packaged client launch gate proves the Windows investor/demo package can be created, opened through a known launcher, and checked through the real-GPU visual QA path.

Required evidence:

• Scripts/PackageWindowsDevelopment.bat completes successfully.
• Builds/WindowsDevelopment/AgrarianGame.exe exists.
• Scripts/InstallWindowsDemoLaunchers.bat installs:
  • Start Agrarian Demo.cmd
  • Start Agrarian Demo - DX12.cmd
  • Start Agrarian Demo - Compatibility DX11.cmd
• Scripts/RunWindowsInvestorVisualQACheck.bat --check-tools reports the packaged demo exists and SunshineService is running.
• Any full visual pass stores notes under Saved\VisualQA\InvestorDemo.

This gate is client-only. It does not require multiplayer server deployment.

Server Launch

The server launch gate proves the MVP gameplay host can start the current server-compatible package and expose the Unreal gameplay port.

Current MVP launch path:

• Prefer the true Linux dedicated-server target when a server-capable Unreal engine is available: Scripts/BuildLinuxDedicatedServer-Windows.bat
• Until then, use the binary-engine fallback: Scripts/PackageLinuxGameServerFallback-Windows.bat
• Deploy the produced package to /opt/agrarian/server.
• Launch through /opt/agrarian/server/AgrarianGameServer.sh.
• Manage the host with agrarian-game-server.service.

Required evidence:

• systemctl is-active agrarian-game-server.service reports active.
• ss -lunp shows AgrarianGame listening on 0.0.0.0:7777/udp.
• The journal shows the Ground Zero map browse started.
• The runbook explains the true dedicated target and fallback path.

This gate is server-relevant and requires multiplayer server verification when server launch tooling or deployed package contents change.