Remove TDD Remove Test-Driven Development Remove Tools
article thumbnail

Agile Book Club: Test-Driven Development (with Mike “GeePaw” Hill and J.B. Rainsberger)

James Shore

Test-Driven Development is one of the few truly new Agile ideas. It’s not perfect, but it’s a powerful tool for creating robust and reliable software. In this session, we’re joined by two folks with decades of TDD experience: Mike “GeePaw” Hill and J. Test-Driven Development. ?? Rainsberger.

article thumbnail

Testing Redux: Strategies and Tools

Perficient

. // Example Jest Test for Selectors test('select only completed todos', () => { const state = { todos: [ { text: 'Use Redux', completed: false }, { text: 'Run the tests', completed: true }, ], }; const expectedSelectedTodos = [{ text: 'Run the tests', completed: true }]; expect(selectCompletedTodos(state)).toEqual(expectedSelectedTodos);

Testing 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

Test-Driven Development. Wouldn’t it be wonderful if there were a tool that alerted you to programming mistakes moments after you made them—a tool so powerful, it virtually eliminated the need for debugging? There is such a tool, or rather, a technique. TDD isn’t perfect, of course. Why TDD Works.

article thumbnail

Xebians collaborating on internal tool development

Xebia

However, the purpose of this blog is not just to describe the toolset, but to share our development approach and some valuable lessons I (re)learned along the way. Our development approach Here is an overview of how we introduce new capabilities into the tool: 1. This typically concludes with the removal of the original code.

article thumbnail

Effective Software Testing – A Developer’s Guide

Henrik Warne

Particularly the chapters on how to systematically come up with test cases based on the specification, inputs, outputs and the structure of the implementation. There can also be implementation details that will not show up in the functional specification, but still need to be tested. The goal here is not to reach 100% test coverage.

article thumbnail

Misconceptions with Test Driven Development

Agile Pain Relief Notes from a Tool User

import Figure from '@/components/global/figure.astro'; import TestXs from 'src/content/blog/misconceptions-with-test-driven-development/images/test-xs.jpg'; In the past few weeks I've heard several misconceptions raised about Test Driven Development: Does TDD really work?

article thumbnail

Test-driven React.js Development: React.js Unit Testing with Enzyme and Jest

Toptal

Therefore, one of the best ways to avoid creating legacy code is using test-driven development (TDD). While there are many tools available to create unit tests in JavaScript and, in this post, we will use Jest and Enzyme to create a React.js component with basic functionality using TDD.