Most developers think that the most beneficial part of using test-driven development (TDD) are the tests. But, when done right, TDD improves the overall design of your code. This installment in the Evolutionary architecture and emergent design series walks through an extended example showing how design can emerge from the concerns that float up from testing. Testing is only a side effect of TDD; the important part is how it changes your code for the better.
Apache JMeter is open source Java desktop software designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.
This post presents good practice for efficient UI test automation.
The article “Writing Testable Code” presents practices to write more testable code with many examples in java, going a step further than just TDD.
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.
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.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates