Software Testing Articles: Load Testing, Unit Testing, Functional Testing

Test-Driven Design, Part 1

April 23, 2010 0

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.

Writing Testable Code

April 2, 2010 0

The article “Writing Testable Code” presents practices to write more testable code with many examples in java, going a step further than just TDD.

Who Perform Functional Testing?

March 15, 2010 0

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.

New Models for Test Development

January 23, 2010 0

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.

How to Regression Test a Relational Database

January 23, 2010 0

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?

Measure Test Coverage with Cobertura

January 5, 2010 0

Cobertura is an open source tool that measures test coverage by instrumenting a code base and watching which lines of code are and are not executed as the test suite runs.

1 32 33 34 35