Published Sep 3, 2019

SE-Radio Episode 283: Alexander Tarlinder on Developer Testing

Alexander Tarlinder delves into the nuances of developer testing, emphasizing specification-based testing, design by contract, and the importance of writing testable code. He discusses balancing test-driven development with practical approaches, while focusing on enhancing software quality through formalized testing responsibilities and methodologies.
Episode Highlights
Software Engineering Radio - the podcast for professional software developers logo

Popular Clips

Questions from this episode

Episode Highlights

  • Spec Testing

    Specification-based testing is a fundamental technique often overlooked by developers. explains that these techniques, such as equivalence partitioning and boundary value analysis, are derived from specifications like user stories or formal documents. Despite their importance, these methods haven't gained popularity in the developer community, remaining largely within the testing world 1.

    Specification-based techniques are fundamental testing techniques for testers, derived from the specification.

    ---

    notes the lack of mainstream discussions on these techniques, highlighting their potential to enhance testing practices 2.

       

    Design Contract

    Design by contract involves formalizing responsibilities between program elements, a concept that finds valuable for generating test cases. He emphasizes that while the constructs supporting this approach aren't primary in popular languages, the mindset of formalized responsibility is crucial 3.

    The essence is the mindset of formalized responsibility between program elements.

    ---

    and Alexander discuss how this mindset aids in determining the number of tests needed, though it's not about embedding formal responsibility in the code itself 1.

Related Episodes