Patch Notes 2.5.0.2 (Destiny)

by dogcow , Hiding from Bob, in the vent core., Tuesday, February 14, 2017, 21:54 (2837 days ago) @ BeardFade
edited by dogcow, Tuesday, February 14, 2017, 21:59

I was just chatting with a former game developer in the UK about test driven development (we were talking specifically to web development). He told me he got so into TDD now because they never did it for game development.

Once you start TDD and writing unit tests, it's hard to go back, and you easily avoid this stuff because you see exactly what you broke with each change.

Just based on this observation, it seems they likely don't have unit tests to know when they break one. Testing does take up a considerable amount of development time, so they may feel they don't have that kind of time to spend. The trade off being you break things inadvertently and spend time later fixing what you broke.

They could probably hire a slew of interns to write unit tests for their code base and avoid this problem in the future.

Oh, I could see them having good test coverage with unit tests for their code, but not for the data that makes up the weapon/armor/ability stats(data?) <edit> and the cascading effects a change can create </edit>. I imagine that's really the root cause of these bugs. It appears they don't "unit-test" their data, looks like they should.