3. “IT TAKES TOO LONG”
• SSD’s are < .50 GB
• Go get a 3/4/6/8/12/16/18/36 core CPU (they are
not that expensive)
• If you are hitting a DB look at In-Memory
repositories / run it locally.
• If you have to spin up an environment - Look at
Docker, Chef, Puppet and VM’s (Azure and
Amazon)
4. ‘The cost to fix a bug goes up
exponentially as you find it later in the
project’
Probably why Destiny cost a billion
dollars :-)
5. “I AM ON (X) HOW DO I
TEST?”
STEP ONE:
Interfaces, interfaces, interfaces, interfaces, interfaces, interfaces,
interfaces, interfaces, interfaces, whatever passes for interfaces in
your language and mocking.
STEP TWO:
Write some d*#n tests! - .Assert() and <obj>.Test() or [Test] is pretty
much universal.
They are just classes that are executed by the test runner
(Think - What is absolute least amount of outside information my
function/method needs for me to test it)
6. But WAIT! Do I do:
Unit? Functional? Integration?
Automation?
a.k.a
How Do I Start?
• It (mostly) doesn’t matter.
• Some testing is better than no testing.
• Different systems test better in certain ways than others.
• Remember, if you don’t have tests you are just changing s#!??
7. Helpful, Non-ranty things.
• Testing frameworks
• Check and CPPUnit - C / C++
• NUnit and XUnit - C# (and other .NET things)
• QUnit and Jasmine - Javascript
8. Even UNITY Has F!#$
Testing Tools
• Unity Test Tools (Open Source!)
• https://bitbucket.org/Unity-Technologies/unitytesttools/wiki/Home
• Code AND IDE drag / drop testing (So even the artists don’t have an excuse!)
• Unity Cloud Build (Beta)
• http://unity3d.com/unity/cloud-build
• Automated builds, URL’s to install on other devices (ala
Testflight)
9. Don’t Be Lazy, Test Your S#!??
We Have Depended On
Manual Testing For Too Long
• Your co-workers won’t want to stab you any more.
• Your testers won’t want to stab you any more.
• Your boss won’t want to stab you any more.
• Your players, will want to stab you but for other reasons.