Tutorials and resources on how to apply unit testing in software testing
A test is not a unit test if: * It talks to the database * It communicates across the network * It touches the file system * It can’t run at the same time as any of your other unit tests * You have to do special things to your environment (such as editing config files) to run it.
Gojko Adzic explains his point of view on the different purposes of Behavior Driven Development and unit tests.
This blog post explores how to do unit testing of javascript using JsTestDriver. The goal of JsTestDriver is to build a JavaScript test runner which easily integrates with continuous builds systems and allows running tests on multiple browsers quickly to ease TDD style development.
This blog post presents the AutoTest.Net tool to continuously test your .net code. AutoTest.NET is a tool for running your unit tests as soon as your save your files.
In this blog post, Cédric Beust describes the new TestNG features that allows to convert Java unit tests from JUnit 3 and JUnit 4 to TestNG.
Mocking frameworks allow you to stub out behavior to perform tests of individual pieces of functionality. However, there are times when performing certain actions and assert a result is not sufficient. This video drills deep into unit testing and explains the differences between state and interaction–based testing. We will examine the role of stubs versus mocks and how to correctly write unit tests that are not fragile or counter–productive. Watch this streaming video from the Norwegian Developer Conference 2010
In this article, Amy Blankenship lists the benefits she has seen from using Test Driven Development (TDD).
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates