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.
Agile software testing tutorials
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?
Performing testing in an Agile context require a completely different approach to software testing activities that is often named “Shift Left”. This term emphasize the move of software quality activities to the beginning of the software development life cycle. In this article, Kishan Sundar shares his perspective about the consequences for Scrum teams of shifting left software testing in Agile.
In theory, we can consider software testing as a very rationale approach. You start from unit of code or requirements and then you create the tests that will prove that your software does what it is expected to do… and doesn’t create problems with edge cases. In his book Oblique Testing, Mike Talks propose to add an additional perspective to software testing using the oblique strategies approach.
Some organizations have published recently reports on the status and the trend of the software testing domain. We have aggregated the main results of these reports in this article to give you an overview of the current software testing issues and practices.
Performing software testing in an Agile project doesn’t mean that it should be improvised. In this article from their book “More Agile Testing”, Janet Gregory and Lisa Crispin looks at some foundations of Agile test planning using the Agile testing quadrants.
10 years ago, Dan North first came up with the idea of Behaviour-Driven Development (BDD): using examples in conversation to explore the behavior of systems, then carrying those examples into code. Since then, we have learned a lot about how BDD works, how it works best, and how it can fail horribly! Even the most experienced BDD practitioners have learned a lot from their failures… but what were they? And how are we failing now?