Agile testing tutorials and how to content : Test-Driven Development (TDD), Behavior-Driven Development (BDD) and other agile approaches for software testing.
PractiTest has released its ninth annual State of Testing® report. This year’s report shows changes in the way software developers think about testing, highlights a shift in the way testers perceive their role, and includes a new section on the impact Agile and DevOps play on testing.
In pursuing the twin goals of increased speed and continuous innovation, delivery teams have been busily ramping up automation efforts in the last few years. Test automation has been instrumental in helping accelerate release cycles, improve software quality and increase efficiency across the whole software delivery lifecycle (SDLC).
Object orientation (OO) is not a trendy concept anymore, but it hasn’t certainly lost it values. The purpose of the book “Growing Object-Oriented Software, Guided by Tests” is to integrate the development of object-oriented software with the Agile testing Test-Driven Development (TDD) approach, more specifically in Java. It starts with an introduction to TDD and the open source testing tools (Junit, jMock2) that will be used in the examples.
In the early days of Agile, methods such as Extreme Programming advocated for shipping without a QA phase. In fact, they often didn’t have dedicated software testers or even bug-tracking systems. And yet there are stories of these teams producing an order of magnitude fewer defects than normal.
PractiTest has released its eighth annual State of Testing© report containing insights from software testing professionals from around the world. This document confirms the growth of test automation and that software testers are working more and more outside their traditional QA silo.
A couple of years ago, Endava realized that the difficulties in DevOps adoption are never the automation technology but rather the ways-of-working, which require a much more fundamental change in people’s behavior and culture.
This video explains how to improve your exploratory testing through LESS preparation but more creativity! One of the characteristics of exploratory testing is that you do less preparation and that you decide on the spot what your next test case will be.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates