Fast feedback on every change you do to your software codebase is essential for a rapid and safe development cycle. Failed test runs need attention from human experts that can quickly analyze and take necessary action. Our problem: the number of failed tests results is higher than our little group …
This talk covers how to write unit tests for your database, which parts you should (and shouldn’t!) test, and how to run your tests automatically on a continuation server (CI) server, after which you will be able to write unit tests for your own SQL code and enjoy database development …
Trompeloeil is an open source thread-safe header-only mocking framework for C++14. It is easy to use while also allowing great expressive power. A popular technique in unit testing is to break dependencies by replacing collaborators of the unit under test with mock objects. Mocking frameworks makes it easier to create …
This talk takes you through the life cycle of a bug in Eclipse from the filing of the bug to the state of commit of the solution of that bug. As all are aware, all the issues are tracked via bugzilla, and the story starts with the creation of the …
Flaky test automation drives everybody nuts. Run it once, it fails, run it again – nope! So you stop running those flaky tests, and everyone is happy until a nasty bug gets in there that those tests would have caught. It’s a trap. If you want to run faster and …
Most of us never know who does the security testing for our development teams. Sometimes it’s an internal team, maybe external. Sometimes it doesn’t even happen at all. Some of us are building security testing into our current practices, from the ground up. Some managers may feel that there isn’t …
