Dror Helper

O autorovi


Dror is a freelance consultant and Architect. He has been writing software professionally for more than a decade, during which he has worked for industry giants such as Intel and SAP as well as small startup companies. He has extensive knowledge of many programming languages and platforms including C++, assembly, .NET (C#/VB) and Java. Dror is a Pluralsight author and public speaker. He is an expert in agile methodologies and software engineering practices. When not writing code, Dror mentors developers and conducts courses about clean code, unit testing and TDD. In his blog (www.helpercode.com) Dror writes about programming languages, software development tools, clean code, cool programming languages and anything else he finds interesting.

Profil tohoto autora byl importován z portálu WUG.CZ

The secret unit testing tools no one ever told you about

Dror Helper 14.11.2019 152
There are more to unit testing than using a unit testing framework - in order to succeed you want to use the right tools for the job.
There are a few tools that almost no one talks about - some enabling creating of top-notch, robust unit tests. Some will help you run your tests better and faster.
In this session I'll explain about the inevitable maintainability problems developers face when writing and maintaining huge unit testing suits and how unit level BDD, AutoMocking, and Continuous Execution can help take control over your tests.
zobrazit více zobrazit méně

Unit testing patterns for Concurrent code

Dror Helper 14.11.2019 148
Getting started with unit testing is not hard, the only problem is that most programs are more than a simple calculator with two parameters and a returns value that is easy to verify.
Writing unit tests for multi-threaded code is harder still.
Over the years I discovered useful patterns that helped me to test multi-threaded and asynchronous code and enabled the creation of deterministic, simple and robust unit tests.
Come learn how to test code that uses concurrency and parallelism – so that the excuses of not writing unit tests for such code would become as obsolete as a single core processors.
zobrazit více zobrazit méně

1