These days testing is considered an increasingly sexy topic for programmers. Who'd have thought it? What is the motivation for unit testing? And what constitutes a good unit test? There's more to effective unit testing than just knowing the assertion syntax of a framework.

Testing represents a form of communication and, as such, it offers multiple levels and forms of feedback, not just basic defect detection. Effective unit testing requires an understanding of what forms of feedback and communication are offered by tests, and what styles encourage or discourage such qualities.

What style of test partitioning is most common, and yet scales poorly and is ineffective at properly expressing the behaviour of a class or component? What styles, tricks and tips can be used to make tests more specification-like and scalable?

Conference: [ Ссылка ]
Slide and Other details: [ Ссылка ]

свернуть