Tutorials and resources on how to apply unit testing in software testing
Intern is an open source software testing tool for Javascript. It runs tests using the browser or node.js and seamlessly integrates with SauceLabs or Selenium. You can write tests using object, TDD, or BDD styles and get full code coverage reporting with Istanbul. This article by Alvin Liu, Todd Kaplinger and Mingzhe Huang provides a presentation of Intern and explains how to use it to test web applications.
One of the most discussed question when people talk about unit testing is what a “unit” is? In this blog post, Ken Baltrinic tries to answer this question.
Better Unit Testing with Microsoft Fakes is a free e-book that discusses the topic of Microsoft Fakes. Microsoft Fakes is a code isolation framework for Visual Studio that helps you isolate the code for unit testing by replacing other parts of the application with stubs or shims. With Microsoft Fakes you can test parts of your software even if some parts have not been implemented or are not working yet.
Test-Driven Development (TDD) can be difficult to practice as features increase in complexity. Testing is often skipped when developers feel uncomfortable with TDD or have not yet seen certain approaches in practice. This video describes specific techniques used in TDD which touch on: Integration testing with RSpec+Capybara, Model Associations and Data Validations, Asynchronous Jobs, Emails, 3rd Party Services, and JSON API endpoints.
It might seem strange that software developers still have trouble understanding. In this article, Jeff Knupp tries to describe what unit testing is, why it is useful and how you should perform unit testing for Python code.
This presentation incrementally demonstrates the concepts of Unit Testing, Test-Driven Development (TDD) and then Behavior-Driven Development (BDD) that enable us not just to create robust regression tests, but also clean and maintainable code.
Tests are supposed to save us money. How is it, then, that many times they become millstones around our necks, gradually morphing into fragile, breakable things that raise the cost of change? We write too many tests and we test the wrong kinds of things.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates