Paul Carvalho joins us to discuss his two sessions at Agile 2012: Pitfalls in Agile Testing and How to Avoid Them and The Zero Page Test Plan
Brian Marick discusses the difficulties met trying to maintain tests that are vital to a project’s success, and how mocking frameworks can help, providing advice on writing unit and integration tests
Martin Fowler and Paulo Caroli discuss testing, continuous integration and continuous deployment, as well as DSLs and REST.
Brian Marick discusses what he means by micro-scale-retro-futurist-anachro-syndicalism and why we should go back to the roots of Agile. He talks about what he thinks were the mistakes in the Agile Manifesto, how it has lead to the state of the Agile community today, and how we can build better systems by making them so that they are much more easily tested.
In this interview from QCon London 2008, Erich Gamma discusses the Jazz project, why Eclipse has been successful, the strict Eclipse release schedule, JUnit, Design Patterns, how to identify a design pattern, design patterns and the 'Don't Repeat Yourself' principle, the design pattern community, and whether dependency injection is a design pattern.
In this interview made during Agile 2007, Dr. Hakan Erdogmus, Editor in Chief of IEEE Software, discusses about TDD starting from a study done by Ron Jeffries and Grigori Melnik and published as "TDD--The Art of Fearless Programming" in the IEEE Software magazine. Hakan talks about current misunderstandings regarding TDD's role in software development and the adoption issues it faces.
In this interview from QCon San Francisco 2007, Cédric Beust discusses designing and architecting for testability, problems that hinder testability, test-driven development, the "Next Generation Testing" book, performance testing recipes, and testing small, medium and large codebases.
Debate sprang up at JAOO '07 around Bob Martin's assertion that "nowadays it is irresponsible for a developer to ship a line of code he has not executed in a unit test." In this InfoQ video, he debated with Jim Coplien on this and other topics, including Design by Contract vs. TDD and how much up-front architecture is needed to keep a system consistent with the business domain model.