Mike Cohn’s Test Pyramid describes a test automation strategy consisting of a wide base of unit tests, service-oriented acceptance tests for business logic, and a thin layer of tests exercising the user interface. Tests that provide the quickest feedback and fault precision serve as the testing foundation. So, how does this work in practice? How does a team achieve this level of test automation and maintain it over time? How can the team avoid redundancy in the various test layers? Jim Weaver demonstrates the different types of tests for a real feature—enforcing business rules for...
Jim Weaver
Jim Weaver is a principal developer and mentor at Vanderbilt University Medical Center (VUMC). Jim has decades of experience building software products in a variety of industries, with a focus on agile practices and mentoring. He is a co-inventor of MyHealthAtVanderbilt, a VUMC patient web portal. Previously at ThoughtWorks, Jim coauthored JWebUnit, an open source web testing framework. At GTE, Jim supported and trained elements of the US Army Signal Corps on network control software he helped build. He regularly works with developers and testers on testing strategies for products built in a variety of languages, and has helped train teams in Extreme Programming. Find Jim on Twitter at @tenoxtweets and on LinkedIn.