Writing Testable Code
The article “Writing Testable Code” presents practices to write more testable code with many examples in java, going a step further than just TDD.
Knowledge
Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
Who Perform Functional Testing?
After the results of a previous poll focused on functional testing automation, I wondered if there was still a great divide between the worlds of development and functional testing. So I did this follow-up question to check who was performing the functional testing.
The Three Rules of Test Driven Development
Over the years I have come to describe Test Driven Development in terms of three simple rules.
Load Testing Relational Databases With JMeter
Apache JMeter is a performance testing tool which is entirely written in Java. Any application that works on request/response model can be load tested with JMeter. A relational database is not an exception: receives sql queries, executes them and returns the results of the execution. This post shows you how easy it is to set up test scenarios with the graphical user interface of JMeter.
Are tools necessary for acceptance testing, or are they just evil?
One of the biggest benefits from acceptance testing for me was that the teams finally get a source of information on what goes on in the system as reliable as the code itself. Without acceptance tests, code is the only thing you can really trust and any other documentation gets outdated very quickly. Acceptance tests stay relevant throughout the project because they are automated, and automated tests are kept up to date in order for them to pass. Automation, and consequently a tool, are necessary to get this benefit.
Debug It!
This book “Debug It!” by Paul Butcher provides a structured approach that will help programmers to identify and remove bugs in code. It is based on a four steps process: Reproduce, Diagnose, Fix, Reflect. For each activity, the author provides practical material on how to perform it.
How Do You Refactor Untested Code?
“Bug fixing often uncovers opportunities for refactoring. The very fact that you’re working with code that contains a bug indicates that there is a chance that it could be clearer or better structured.”