Headframe_Studio/MamaMahjong
Headframe_Studio/MamaMahjong
2
0
Fork 0
Code Issues 8 Pull requests Projects 1 Releases Packages Wiki Activity Actions

[Tech]: Unit-Tests für bestehendes Projekt schreiben #16

New issue
Closed
opened 2026-01-29 12:26:16 +00:00 by FlorianReetz · 3 comments
FlorianReetz commented 2026-01-29 12:26:16 +00:00
Owner
Copy link

Unit-Tests mit der GD Test Suite für:

  • Tile
  • BoardArray
  • BoradLayout
  • BoardManager

schreiben. ggfs Konventionen für Unit-Tests verfassen.

Unit-Tests mit der GD Test Suite für: - [x] Tile - [x] BoardArray - [x] BoradLayout - [x] BoardManager schreiben. ggfs Konventionen für Unit-Tests verfassen.
FlorianReetz commented 2026-01-29 22:44:56 +00:00
Author
Owner
Copy link

Tests für BoardLayout müssen nach Refactoring neu geschrieben werden. Betrifft dieses Issue & #17

Tests für BoardLayout müssen nach Refactoring neu geschrieben werden. Betrifft dieses Issue & #17
FlorianReetz added reference test/16-board-manager-unit-tests 2026-02-02 21:52:22 +00:00
FlorianReetz commented 2026-02-02 21:53:02 +00:00
Author
Owner
Copy link

Unit Tests wurden neu geschrieben. BoardManager Tests müssen noch finalisiert werden.

Unit Tests wurden neu geschrieben. BoardManager Tests müssen noch finalisiert werden.
FlorianReetz commented 2026-02-04 16:58:17 +00:00
Author
Owner
Copy link

Issue to Review

Issue to Review
Sign in to join this conversation.
test/16-board-manager-unit-tests
Branches Tags
Clear current reference
main
code/k-editor-tool
dev
Clear current reference
No results found.
Labels
Clear labels   
1| type: bug

bug found. open new issue with this label

  
1| type: documentation

flags a task as documental work

  
1| type: feature

new experience-relevant addition to the project

  
1| type: fix

not a bug but an adjustment request within the games parameters

  
1| type: refactor

overhaul of legacy code

  
1| type: spike

analytical task, decision making, follow up tasks

  
1| type: tech-debt

optimizing system, not refactoring, but technical overhaul

  
2| prio: critical

show stopper, blocks other tasks, core systems affected, build not executable

  
2| prio: high

relevant to current milestone, contribution to customer experience

  
2| prio: low

cosmetical tasks, qol tasks, optimization tasks, can be delayed

  
2| prio: medium

important but no blocker, can be delayed in favour of other tasks

  
3| diff: complex

task requires architectual decisions, multiple dependencies, requires iterations

  
3| diff: exploratory

task is open to definition, needs prototype (own branch), technical or architectual risks

  
3| diff: standard

task is defined, needs integration, known patterns, lokal dependencies

  
3| diff: trivial

task is well defined, low dependencies, no risks (creating a scene, adding a lable, changes in config)

  
4| area: animation

animation work

  
4| area: art

new asset production or integration

  
4| area: audio

audio asset production or integration

  
4| area: gameplay

new gameplay relevant feature

  
4| area: tech

technical or architectual issue

  
4| area: ui / ux

ui or ux relevant task

  
9| extra: blocked

mark a task with this label if it is blocked by another issue

No labels
1| type: bug
1| type: documentation
1| type: feature
1| type: fix
1| type: refactor
1| type: spike
1| type: tech-debt
2| prio: critical
2| prio: high
2| prio: low
2| prio: medium
3| diff: complex
3| diff: exploratory
3| diff: standard
3| diff: trivial
4| area: animation
4| area: art
4| area: audio
4| area: gameplay
4| area: tech
4| area: ui / ux
9| extra: blocked
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
MamaMahjong Development Board
Assignees
Clear assignees
No assignees
FlorianReetz
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Headframe_Studio/MamaMahjong#16
No description provided.