BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Unit Testing Content on InfoQ

  • Presentation: System Integration Testing with Spring

    Spring provides a holistic solution that makes your application's use cases and subsystems easier to test. The emphasis is on testing outside a JEE server or container, thus greatly improving productivity. In this presentation, Spring Creator Rod Johnson discusses integration testing and the support that Spring provides for it.

  • JUnit 4.4 Released

    The release of JUnit 4.4 sees the inclusion of the assertThat method, offering easier reading and new flexibility to the JUnit library.

  • Separating Views from Business Logic with Acropolis

    Microsoft's GUI toolkits tend to encourage developers to tightly couple business logic with presentation. Comparing the original VB and ASP or WinForms and ASP.Net, one sees very little change in this regard. Acropolis is different though, and for the first time since MFC it looks like Microsoft is taking the concept of separation of concerns seriously.

  • Article: Unit-Testing XML

    In this exclusive InfoQ article, Stefan Bodewig explains how to use the XMLUnit Java framework to write tests in the presence of XML.

  • Friend Assemblies and Unit Testing

    A little known C# feature known as friend assemblies will be making its way to VB 9. This feature allows an assembly to grant access to its internals to another assembly.

  • Google SoC Series: Creating RSpec specs for Ruby runtimes

    The number of Ruby implementations grows steadily, but something is missing: a Ruby specification. The behavior of the Ruby language and its standard libraries is defined in the code of the main Ruby implementation. Two Google SoC projects aim to fix this by creating executable RSpec specifications for Ruby. We caught up with Pedro Del Gallego who works on one of these projects.

  • Unit Testing Tips from Google

    The QA engineers at Google share their unit testing advice in an ongoing series titled "Testing on the Toilet." The latest installment tackles a common problem: how can the unit tests themselves be refactored without accidentally invalidating the tests?

  • Matrix Your Rails Functional Tests

    Following the DRY process philosophy and putting into practice separation of concerns, Ryan Davis introduced an interesting way of answering the question: How do you make testing complex specifications with many edge cases clearer? The answer: Matrix!

  • Testing: Manual or Automated?

    Automated testing is all the rage, but is it everything? Micahel, a Test Technical Lead at Microsoft, asks "How do you know whether you have automated enough - or too much?"

  • Microsoft Unit Testing Moved to VS Pro

    Finally recognizing that non-enterprise developers want access to integrated unit testing, Microsoft has made some of its unit testing functionality available in Visual Studio Pro.

  • TestDriven.Net Once Again Supports VS Express Editions

    TestDriven.Net has restored and enhanced support for the Visual Studio Express Editions in the 2.5 beta despite tensions between Jamie Cansdale and Microsoft over license concerns.

  • Understanding Legacy Code with Characterization Testing

    Alberto Savoia has written a series of four articles describing "characterization testing" - the process of writing unit tests to understand and work with legacy code.

  • Test-Driven Database Development with DbFit

    Gojko Adzic has released DbFit, an extension of the Fit testing framework enabling test-driven development against Oracle databases.

  • Tutorial: TDD with Selenium and Castle

    Dan Bunea shows how TDD can be applied in .NET using Selenium RC and Castle. Test first principals provide architects a way to quickly jump into active development early in the application development lifecycle. The benefits of TDD are a drastic reduction in defects as well as increased flexibility in the code base since the application evolves quickly through an iterative process.

  • Heckle Your Way to Better Tests

    Like Jester, the Java program that inspired it, Heckle mutates your Ruby code, attempting to make your unit tests fail. The premise is simple: If your unit test doesn't choke on Heckle's mutated code, then you need to improve coverage.

BT