This presentation gives you a few code review tips for keeping your code healthy and your team happy. You will learn why talking about code in person is important, how to talk about code without burning bridges and, most importantly, how to take dread out of your workplace.
Tomek Kaczanowski writes that the idea behind its “Bad Tests, Good Tests” book is “to present test code snippets and discuss ways of making them better.” To achieve this goal, he explores a large amount of code and tests to discuss all the issues that you can meet in your software testing activities.
Personas are fictional archetypes based on the real world that represent a group of users who have common goals. This is a concept that is often used in product and software development. In this blog post, Katrina Clokie expand the concept of personas to the software testing domain.
Bug Magnet is an open source Chrome extension that provides an easy access to common software testing problematic values and edge cases. You will be able to access them easily during exploratory testing sessions so that you can fill the tested fields with a chosen value. A Firefox equivalent has also been developed.
Maintaining the devices that your company provides for testing mobile applications is mandatory for the success of your mobile development projects. It is as important as the human resources of the company. Since modern emulation tools and cloud services don’t assure high quality of mobile applications, all portable devices such as smartphones and tablets should be maintained properly. This article explains how you can extend their lifespan.
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.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates