In this session, we’ll test some real small to medium size applications for quality and bugs. Through three main activities of collation, investigation and prediction, we’ll move through our explorations understanding applications then experimenting with discovery and failure situations, utilizing tools when relevant. While Erik will guide the session and explain the context, a large part of the testing will come from the audience, either as ideas or driving the keyboard. While this is accessible as an introductory session, it will also show how to perform industrial strength ET.
How can mock objects help you design your system better? Want to know how mocking saved hours of work? We focus on establishing best practices based on examples with mock objects. We cover design of classes, using mock objects to understand and test interaction between objects of the system. By the end of the session it should become clear how mocking,when applied correctly helps with system design, improves testability by reducing cost of change. An explicit part of this session is dedicated to the Mocking top offenders. We talk with examples about bad usage of Mocks, and its consequences.
A Continuous Integration system is often considered one of the key elements involved in supporting an agile software development and testing environment. As a traditional software tester transitioning to agile environment, it became clear that we would needed several changes to make the transition to agile testing possible. This experience report discusses a continuous integration implementation I led last year. The initial motivations, technical specifics of the implementation, perceived benefits to the team, and retrospective results are all discussed.