Agile testing tutorials and how to content : Test-Driven Development (TDD), Behavior-Driven Development (BDD) and other agile approaches for software testing.
There is a lot of talk in modern software testing teams about experimentation. Classically an experiment is a very structured series of activities designed to find something out. Sounds a lot like software testing and is in direct alignment with the concepts around Test-Driven Development (TDD), Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD). This video discusses how to design testing experiments that are valuable and provide the right insights to the right people, at the right time.
When a software development team switches its approach to an Agile framework like Scrum, the place of software testing changes. In his book Scrum Product Ownership, Robert Galen describes the new role of software testers in Agile teams and their relationships with the product owners.
Doing software testing in production used to be taboo – a sign that you had a lax attitude to QA. Now it is increasingly accepted that the opposite is true, and that if you only test your system in artificial environments you don’t really know it works. This presentation shows the tools and techniques used to test feature functionality, performance, and failure scenarios in production.
Shift Left Testing is the name applied to the Agile concept to shift the software testing activities from the end of the software development life cycle to its beginning, or on the left of life cycle diagrams. In his article “Four Types of Shift Left Testing”, Donald Firesmith of the Software Engineering Institute discusses the importance of shift left testing and defines four different approaches to implement shift left testing.
Software testing can be an isolated activity. While some project activities are done in a team, test execution is typically performed alone. However the concept of pair programming, a well-known practice of eXtremme programming and Agile software development, can also be applied to software testing. This presentation explains how TradeMe pairs testers to remove silos, passively educate, and increase the efficiency of testing.
Test Engineering culture emphasises on quality ownership by all involved in a project and redefines the role of testers as engineers as quality enablers instead of gate keepers. This talk shares the experience to build a test engineering culture across the organization, how does it vary with the size of the team and the company and the role of software testersin building this culture by enabling others with tools and processes for quality improvements.
Most research on Agile Testing and QA have requirements on highly automated testing/CI and an Agile or Scrum project-management structure. How can we iterate towards a more Agile testing process, with all the benefits that entails, when some of the common requirements are missing or undesirable in the near-term?
