SDC

Minutes before my talk Marcel was desperately trying to get in touch. My badge for speaker was left at the check-in counter and my phone was on “do not disturb”. Marcel found me setting up my laptop and already figured out what happend: I registered as visitor and got that badge on check-in.

The previous speaker used a MacBook. I did saw a lot of MacBooks that day, but many noticed that. Someone moved the projector for best viewing the specific resolution output of the VGA adapter a MacBook user needs. This special setup was unfit for my HP Windows laptop. Luckily the guy who “fixed” the projector came walking in and solved this issue for me. Time to start.

As a first time speaker I did not expect this crowd. Some extra chairs were needed.

Everybody was a developer (I asked) and that was my kind of people. Silent in the beginning and more interactive at the end. No powerpoint screenshots of code in my talk, but live coding of my demo’s. That is what set me apart. Laughter when my automatic builds all failed and super feedback / thumbs up during lunch and in between talks. Will try to do this more often.

Questions

After the slides all that is left are questions and answers.

Tests that hit the database can be slow, how to deal with those? These are integration tests and not unit tests. A unit test is isolated from databases because existing data could impact the test as could locked users and dropped tables. A unit test only tests a (very) small part of the software and is isolated from other parts. Put the integration tests in a different project and only run them when you do integration testing (which can take a long time).

I’ve got one question about test lists in Visual Studio 2010. What has 2013 to offer as it lacks this test lists feature? After some discussion someone pointed out we could create a playlist file. I never noted this option as I did not need it. The build simply runs all unit tests and I’m lucky enough to have Visual Studio premium which has the “run tests on build” option that is smart enough to only run tests that are impacted. Nice to learn something on my own talk 😉

References

• Slides
• TransportDemo code on github
• Filter unittests with custom playlists in VS2013
• Visual Studio 2013 keyboard shortcuts