asrob-uc3m / asrob-uc3m/robotDevastation

Add setup of preconditions in FSM test using previous states directly

Open
#46 2 comments 0 reactions 0 assignees View on GitHub
priority: idea
Dominant language
C++
Stars
9
Forks
4
PR merge metrics
No merged PRs in 30d

Description

As it is done in testGameState, all preconditions can be setup by using previous states code directly. This is error-proof, as the previous states are also covered by unit tests.

This is done in testGameState this way, and could be done in testDeadState in a similar way.

Contributor guide

Open the contributing guide

Research direction

Compare the existing precondition setup in testGameState with the setup in testDeadState. Reuse the previous-states approach in testDeadState, then run the FSM tests and confirm that the test still reaches the intended dead state without manually duplicating preconditions.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev, testing
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.