It's easy to write a unit test that says, "When I shoot a dude with this gun, make sure his health goes down by 50". But it's an entirely different thing to say something like, "Make sure that when a battle is going on nobody gets caught up on geometry and can't path to their movement goal."
You're right, those types of rules are not easily tested with unit tests. In fact they are impossible to test with unit tests. Instead they are tested with integration and/or acceptance tests. These are the tests that the QA department creates and executes. Just because you are doing agile/test first dev with unit tests doesn't mean QA goes away, only that generally the responsibility for catching the fact that you used a != instead of == is yours and not the QA engineer's.
Well much of the content that they are releasing with the patches is content that was intended to be included at release. Descriptions of the honor system and battlegrounds are in the game manual.
This is a niche genre that I honestly wish someone would make more games for.
My pick. XCOM - I simply loved this game.
Certainly genre defining as there were several games made later mirroring it. Jagged Alliance and all the crappy attempts to create "real time" counterparts (Fallout Tactics excluded from the crappy qualifier).
Agreed. Combat Mission rekindled my interest in historical war games. I keep a pretty regular PBEM game with a friend of mine. It's especially good for large games where you need a good deal of time to set up and execute a complex strategy.
It uses a phased turn based style where both players give orders to their troops (like Laser Squad Nemesis) and then you watch game "run" for a minute as the troops for both sides try to execute their orders at the same time.
I am wondering the same thing myself; If all it's doing is scraping the screen buffer somehow, I don't see why not.
my guess is #3... It's the only move that makes $1.6B make sense
You're right, those types of rules are not easily tested with unit tests. In fact they are impossible to test with unit tests. Instead they are tested with integration and/or acceptance tests. These are the tests that the QA department creates and executes. Just because you are doing agile/test first dev with unit tests doesn't mean QA goes away, only that generally the responsibility for catching the fact that you used a != instead of == is yours and not the QA engineer's.
Well much of the content that they are releasing with the patches is content that was intended to be included at release. Descriptions of the honor system and battlegrounds are in the game manual.
This is a niche genre that I honestly wish someone would make more games for.
My pick.
XCOM - I simply loved this game.
Certainly genre defining as there were several games made later mirroring it. Jagged Alliance and all the crappy attempts to create "real time" counterparts (Fallout Tactics excluded from the crappy qualifier).
Agreed. Combat Mission rekindled my interest in historical war games. I keep a pretty regular PBEM game with a friend of mine. It's especially good for large games where you need a good deal of time to set up and execute a complex strategy. It uses a phased turn based style where both players give orders to their troops (like Laser Squad Nemesis) and then you watch game "run" for a minute as the troops for both sides try to execute their orders at the same time.