Differences

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

--- documentation:rtsprogrammingguidelines [2013/06/06 07:42] – created mhgamework
+++ documentation:rtsprogrammingguidelines [2024/08/26 13:25] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== RTS Testcase 1 Programming guidelines ======
-In short
+In short the guidelines are.
-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).
+  * One sandbox test combining all features, implemented using ModelObject system.
+  * Unit tests for IoC based components
+  * No Unit tests for simulators, only use them for the sandbox test.
+  * Simulator hard to test or to big? Convert to component and unit test!
-Next there is the actual 'biiiig' test that works with the Simulator and ModelObject framework to combine all these features into the actual RTS game.
+===== Detailed explanation =====
-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.
-Also: found a way to define when something should be in the simulators and when it should be written using IoC. If you wrote a unit test, it should be IoC (and pls do).
+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 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.