Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add unit tests for GameEngine command handling

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
game-dev, testing-qa

Research direction

Start by reading the GameEngine command handling and the existing tests for CommandParser, ConditionEvaluator, NarratorService, SaveManager, and WorldValidator. Create GameEngineTests.cs using mock IOutputWriter/IInputReader, cover the listed go, take, use, talk, and save/load scenarios, and confirm the GameEngine has coverage for each case.

Written by the indexing model from the issue text.

Description

squad:barton testing

The test suite covers CommandParser, ConditionEvaluator, NarratorService, SaveManager, and WorldValidator but GameEngine itself has zero test coverage. Create GameEngineTests.cs with mock IOutputWriter/IInputReader. Test each command handler: go (locked exit), take (non-portable), use (puzzle solve), talk (givesItem), save/load round-trip.

Dominant language
C#
Stars
1
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from csharpfritz/MyFirstTextGame

All issues in csharpfritz/MyFirstTextGame

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.