Once you start to get good at Test-Driven Development (TDD), you begin to learn the nuances of the discipline such as the fact that tests and code grow in very opposite directions. As the tests get more specific, the code gets more generic.
Software developers have often the habit to write code faster than their software testing capabilities. This creates a backlog of untested code. In this blog post, Dennis Stevens proposes some hints about things that programmers can do instead of writing untested code.
Let’s have a close look into the Red-Green-Refactor cycle and understand the subtleties of each step. When we go down the rabbit hole of Test Driven Design (TDD), we sometimes take too big steps leading us to many failed tests we just can bring back to green without writing a lot of code. We need to take a step back and take the shrinking potion of baby steps again.
It is not always easy to have management responsibilities in software development and software testing when you come from a technical position. This is also true in software testing. In this article, Mark Garzone shares some tips on how to be a better software testing team lead or test manager.
This presentation looks at the chasm-crossing potential of Test-Driven Development (TDD) and some related technologies. The aim is that you will still be able to get a good job in 2024.
Writing unit tests is easy in theory but could be more difficult in practice. Usually experience helps in getting better at unit testing. In this blog post, Patroklos Papapetrou shares some of his experience in writing Java unit tests.
Behaviour Driven Development (BDD) is an Agile practice that aim at merging requirements documentation and software testing. What makes this technique different is that it engages Stakeholders from start to finish of a project. This is done by writing Specifications by Example in collaboration with all Stakeholders.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates