This talk try to answer the question of what the software quality assurance (QA) team should be doing, and how it is not only more fruitful for the software development organization, but a more rewarding path for the Testing Craftsman.
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.
If a SQL server is the bedrock of your app or service, then its performance will be a big part in determining the responsiveness and fluidity of the end-user experience. As such, it is only by monitoring database performance from moment to moment and tracking usage trends over time that you can optimize it successfully.
How does your team or organization measure quality? People often equate software testing to good quality. If you have good testing practices, does that mean you have a good quality software product? Many teams measure process quality and don’t realize they forget about the product quality – which is what the customer cares about.
You have to assess the risks and the benefits of every decision you make in software testing and quality assurance. In this article, Sandra Parker explains how to minimize the risks of outsourcing your software QA activities.
Continuous testing, continuous delivery, DevOps – these are all terms very popular in the last couple of years, and they all involve a shift in the way we deliver products, software testing included! So who is responsible for the quality assurance nowadays?
There are many books about software testing, but Quality Code is among the best that I have read. It presents a philosophy about software testing that has been mine in my previous life as a software developer: the programmer is the main person responsible for the quality of its code.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates