The Three Rules of Test Driven Development
Over the years I have come to describe Test Driven Development in terms of three simple rules.
Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
Over the years I have come to describe Test Driven Development in terms of three simple rules.
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.
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.
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.
“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.”
This paper does two things. First, it attempts to demolish a bad model, the quite popular “V model”. In the process, it hopes to banish the phrases “unit testing” and “integration testing” from our vocabularies. Second, it describes a better model. The primary purpose is not to claim to have the right model, but to describe important requirements for test models. Those requirements are summarized at the end of the paper.
This article overviews the importance of, and strategies for, regression testing relational databases. If your organization considers data to be a corporate asset and/or you’re implementing mission-critical functionality within your databases, shouldn’t you have a database testing strategy in place?
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates