The Wizards Wiki

Explore your world

User Tools

Site Tools


documentation:rtsprogrammingguidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
documentation:rtsprogrammingguidelines [2013/06/06 07:52] mhgameworkdocumentation:rtsprogrammingguidelines [2024/08/26 13:25] (current) – external edit 127.0.0.1
Line 10: Line 10:
 ===== Detailed explanation ===== ===== Detailed explanation =====
  
-All game logic is written using decent 'mh responsibility driven design', also called Inversion of Control. Components implemented are all unit tested (as automated as possible).  
  
-Next there is the actual 'biiiigtest that works with the Simulator and ModelObject framework to combine all these features into the actual RTS game.+All game logic is written using decent 'mh responsibility driven design', also called Inversion of Control. Components implemented are all unit tested (as automated as possible).
  
-Note: is is allowed to make more than 1 big test, but the reason of creating these extra tests should not be for testing features, but for cross cutting concerns like: performance, network sync, ...  
-This bigtest should not be considered a unit test (it isnt a unit test), but more like a sandbox environment. 
  
-When should something be in the simulators, and when should something be in the IoC components? When you write a unit test, implement it as a component. There is no point in unit testing simulators.+Next there is the actual big 'sandbox' test that works with the Simulator and [[:documentation:modelobject|ModelObject]] framework to combine all these features into the actual RTS game.
  
 +
 +Note: is is allowed to make more than 1 sandbox test, but the reason of creating these extra tests should not be for testing features, but for cross cutting concerns like: performance, network sync, … This sandbox test should not be considered a unit test (it isnt a unit test), but more like a sandbox environment.
 +
 +
 +When should something be in the simulators, and when should something be in the [[:documentation:ioc|IoC]] components? When you write a unit test, implement it as a component. There is no point in unit testing simulators.
  
documentation/rtsprogrammingguidelines.1370505125.txt.gz · Last modified: 2024/08/26 13:57 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki