Azure Test Plans vs GameCI

Azure Test Plans gives teams tools to plan, run, and track manual and exploratory testing for apps. For scripted tests, teams can track actionable defects and connect test cases and suites to user stories, features, or requirements. Exploratory sessions let testers design and run tests at the same time. During manual tests, Test Runner can capture screenshots, image action logs, and screen recordings. Reports, dashboard widgets, and customizable Power BI reports show plan progress and trends. The service integrates with Azure Pipelines for CI/CD testing and offers REST APIs and an extension contribution model. Manual testing is available in the web portal through supported browsers on major platforms; a free Test & Feedback extension supports exploratory testing in Chrome and Microsoft Edge. The free Stakeholders plan does not allow users to create or manage Test Plans. Basic is free for the first five users, then $6 per user per month; Basic + Test Plans costs $52 a month, billed at $52 per user per month. A 30-day trial is listed. Azure DevOps cloud-based load testing is deprecated; Microsoft points users to Azure Load Testing for managed load testing.

GameCI provides free, open-source tools for automating game project builds, tests, and deployments. Unity is its primary maintained engine package, with official containers, GitHub Actions, licensing flows, build targets, and documentation. Its CLI also detects Unreal Engine and Godot projects and includes build commands for both; a plugin API can connect additional engines. Officially supported CI/CD platforms are GitHub Actions, GitLab CI, and CircleCI. Listed build targets include iOS, Android, Windows, macOS, Linux, and WebGL. For Unity, the Test Runner supports All, PlayMode, EditMode, and Standalone modes. Results can appear as GitHub status checks if the workflow has write permissions and a GitHub token, or be uploaded as artifacts. GameCI says it does not acquire or store Unity credentials supplied for activation during build and test steps. Self-hosting is described for bare-metal machines, virtual machines, or Orchestrator; operators handle operating-system configuration and lifecycle management. The project is maintained by volunteers and offers best-effort community support, not premium support. CI provider build minutes may cost extra.