Wojciech Seliga shares from experience how complex it can be to deal with thousands of tests -unit, functional, integration, performance- for Atlassian JIRA and what they did to bring it under control.
Patrick Smacchia shares code analysis-related practices -structuring code, measuring code quality, automated tests, code contracts, reporting progress, trending- based on his experience with NDepend.
Janet Gregory explains how testing activities are included throughout the Agile process, and how a tester can add value, discussing ATDD (Acceptance Test Driven Development), and exploratory testing.
Terry Bunio outlines the requirement of a tSQLt-based ETL test framework, showing how tests execute in a demonstration.
John Hughes discusses automated testing techniques that can catch more code defects, with war stories from the likes of Ericsson, Volvo Cars, and Basho Technologies.
Craig Atkinson presents the advantages of using the Geb functional testing library for creating robust and readable tests with both JUnit and Spock, and configuring Geb for testing across multiple browsers.
Adrian Smith covers symptoms, root problems and guidance on recommended solutions for avoiding automated testing mistakes.
Ken Kousen covers the testing options for Grails applications including testing constraints, using mocks, generating test data, the available testing annotations, and more.
Alan Griffiths shares the organizational process, the technological challenges and the solutions adopted by a team developing a C++ systems component.
Zsolt Fabok presents several methods that can be used to find areas which are worth testing so that organizations do not have to spend more effort on testing than what is absolutely necessary.
John Penix describes the test automation system and the supporting build system infrastructure used by Google.
Zsolt Fabok provides guidance on selecting those sections of code that are most likely to profit from automated testing and leaving out those where chances for errors are low.