Kata de TDD by Jordi Anguela
•
0 likes•189 views
These are the slides of the TDD kata event organised at URV university. Slides are meant to be an introduction into TDD, explaining why this methodology improves the software development cycle, reducing its costs and assuring it's quality.
Report
Share
Report
Share
Download to read offline
Recommended
Test Driven Development by Sameer Arora
Test-driven development (TDD) is a software development process where test cases are developed before code to validate requirements. The TDD process involves repeatedly writing a test, making it fail, then writing code to pass the test and refactoring code. TDD results in code with fewer defects, quicker feedback, and requirements that drive design. Tests cover valid and invalid inputs, errors, boundaries, and everything that could break. TDD improves development cycles, defects, documentation, and competitive advantage for businesses.
Jdojo@Gbg Introduction
This document discusses test-driven development (TDD) and its benefits. It notes that TDD can find bugs earlier and reduce costs, though traditional testing is still needed. TDD involves writing a test first, then code to pass the test, and refactoring code while ensuring all tests remain passing. Practicing TDD through coding "katas" or exercises in a "dojo" setting can improve skills over time through repetition. While TDD takes more initial time, the benefits are more confidence, productivity, reliability and agility in the long run.
Exceptions: Why, When, How and Where!
A presentation that shows from where Exception came, how to use them, when to use them, why to use them with a implementation example in Ruby
Developers’ mDay u Banjoj Luci - Milan Popović, PHP Srbija – Testimony (about...
This document discusses the importance of testing software. It outlines 30 tips for writing tests, including writing tests before code, treating tests like code, minimizing asserts per test, using data providers, and allocating time for testing in estimates. Testing helps catch bugs, improve code quality, and ensure stability. The document emphasizes that automated testing is key and should test everything that could break an app.
Tdd
The document discusses Test Driven Development (TDD). TDD is a software development process where test cases are written before implementation code to specify requirements, with code only written to pass newly created tests. The TDD cycle involves writing a test, running the test which fails with no code, writing minimum code to pass the test, running all tests which should now pass, and refactoring code before repeating. Examples like calculating prime number sums and FizzBuzz are provided. Benefits of TDD include improved code quality, reduced bugs, and faster development through continuous testing and feedback. Best practices include pair programming, test planning, and using testing frameworks.
Coderetreat @ CodersTUG
This document outlines an agenda for a coderetreat event. It includes:
- An introduction that describes the event organizer and purpose of learning through sharing.
- An agenda with sessions on test-driven development, extreme programming, cost of change, simple design principles, and mechanics of TDD.
- Descriptions of pair programming, test-driven development, and the Game of Life cellular automaton that will be used in exercises.
- Logistical details like session structure, pairing rotations, and expectations around deleting code between sessions.
Test Driven Development
This document discusses test-driven development (TDD) and unit testing. It defines TDD as a process that involves writing a failing test first, then implementing code to pass that test, and refactoring if needed. Key benefits of TDD and unit testing include reduced bugs, lower maintenance costs, and improved code design. The document provides guidelines for writing good unit tests and emphasizes that tests should be quick, isolated, and answer what behavior was tested and what the expected and actual results were.
Test Driven Development
This document discusses test driven development (TDD) and how it can be applied to legacy code. It describes the TDD process and patterns for writing tests. When applying TDD to legacy code, it recommends identifying change points and inflection points in the code. Tests should be written to cover the inflection point by breaking dependencies. Then changes can be made using the full TDD process, and the covered code can be refactored.
Recommended
Test Driven Development by Sameer Arora
Test-driven development (TDD) is a software development process where test cases are developed before code to validate requirements. The TDD process involves repeatedly writing a test, making it fail, then writing code to pass the test and refactoring code. TDD results in code with fewer defects, quicker feedback, and requirements that drive design. Tests cover valid and invalid inputs, errors, boundaries, and everything that could break. TDD improves development cycles, defects, documentation, and competitive advantage for businesses.
Jdojo@Gbg Introduction
This document discusses test-driven development (TDD) and its benefits. It notes that TDD can find bugs earlier and reduce costs, though traditional testing is still needed. TDD involves writing a test first, then code to pass the test, and refactoring code while ensuring all tests remain passing. Practicing TDD through coding "katas" or exercises in a "dojo" setting can improve skills over time through repetition. While TDD takes more initial time, the benefits are more confidence, productivity, reliability and agility in the long run.
Exceptions: Why, When, How and Where!
A presentation that shows from where Exception came, how to use them, when to use them, why to use them with a implementation example in Ruby
Developers’ mDay u Banjoj Luci - Milan Popović, PHP Srbija – Testimony (about...
This document discusses the importance of testing software. It outlines 30 tips for writing tests, including writing tests before code, treating tests like code, minimizing asserts per test, using data providers, and allocating time for testing in estimates. Testing helps catch bugs, improve code quality, and ensure stability. The document emphasizes that automated testing is key and should test everything that could break an app.
Tdd
The document discusses Test Driven Development (TDD). TDD is a software development process where test cases are written before implementation code to specify requirements, with code only written to pass newly created tests. The TDD cycle involves writing a test, running the test which fails with no code, writing minimum code to pass the test, running all tests which should now pass, and refactoring code before repeating. Examples like calculating prime number sums and FizzBuzz are provided. Benefits of TDD include improved code quality, reduced bugs, and faster development through continuous testing and feedback. Best practices include pair programming, test planning, and using testing frameworks.
Coderetreat @ CodersTUG
This document outlines an agenda for a coderetreat event. It includes:
- An introduction that describes the event organizer and purpose of learning through sharing.
- An agenda with sessions on test-driven development, extreme programming, cost of change, simple design principles, and mechanics of TDD.
- Descriptions of pair programming, test-driven development, and the Game of Life cellular automaton that will be used in exercises.
- Logistical details like session structure, pairing rotations, and expectations around deleting code between sessions.
Test Driven Development
This document discusses test-driven development (TDD) and unit testing. It defines TDD as a process that involves writing a failing test first, then implementing code to pass that test, and refactoring if needed. Key benefits of TDD and unit testing include reduced bugs, lower maintenance costs, and improved code design. The document provides guidelines for writing good unit tests and emphasizes that tests should be quick, isolated, and answer what behavior was tested and what the expected and actual results were.
Test Driven Development
This document discusses test driven development (TDD) and how it can be applied to legacy code. It describes the TDD process and patterns for writing tests. When applying TDD to legacy code, it recommends identifying change points and inflection points in the code. Tests should be written to cover the inflection point by breaking dependencies. Then changes can be made using the full TDD process, and the covered code can be refactored.
Unit testing for project managers
This presentation gives you the evidence as to why unit testing works and a process for how to bring it your team as soon as possible. There's a reason why the growth of unit testing, and automated unit testing in particular, has exploded over the past few years. It not only improves your code, it's faster than releasing code without tests. You'll learn: What, exactly, is a unit test?; The 7 reasons why managers love unit testing; and how to change mindset and processes to start unit testing now.
TDD with RSpec
This document provides an introduction to unit testing with RSpec. It explains that unit tests check individual sections of code and integration tests check how those sections work together. It then describes the red-green-refactor process of test-driven development, where you first write a failing test, then pass the test with the simplest code, then refactor the code. Resources for learning more about RSpec and practicing tests are also provided.
Test Driven Development Part 1
TDD benefits
Clean Design
Fast Feedback
Concrete Evidence That Your Software Works
Write Better Code
Reduced Gold-Plating
Regression Test Suite
How To Do TDD
Analyze the requirements and write the list of tasks or features
Pick a task or feature
Brainstorm a list of tests for the task or feature
Review the tests list and pick a test
Write the test case
Run the test case and see it fails to compile
Write only enough code that the test case compiles
Run the test and see running the code fails
Write only enough code to just pass the test
Refactor the production code and eliminate duplication
Repeat
TDD and Getting Paid
Test-driven development is generally regarded as a good move: it should result in simple decoupled design, your tests tend to cover behaviour not methods, and far fewer bugs. However, just getting unit tests in on a real, commercial project is hard - switching to TDD is even harder. Often you can start a project with good intentions and coverage, then the deadline looms and the tests go out then the hacks come in. So, instead of beating ourselves up about not being perfect let's look at an interative approach to adopting TDD principles. We'll look at tactics for selling TDD to your client, boss and colleagues. This talk will also cover methods for making TDD easier for you by showing you what tools you can use to integrate it into your development environment. In the project itself, we'll examine how we can make small but permanent steps towards full TDD, without losing that progress when deadlines hit. We'll also cover a few methods for learning on your own time and how the whole process can actually be made quite enjoyable.
通往測試最高殿堂的旅程 - GTAC 2016
The Google Test Automation Conference (GTAC) is an annual test automation conference hosted by Google. 2016 is 10th GTAC. I'll share the most impressive parts of experience sharing & tool I heard in GTAC 2016 in this slide.
Why agile testing isn't working
The document discusses challenges with the traditional waterfall process and separating testing from development in Agile. It advocates for a whole team approach where testers and developers collaborate throughout the sprint. Specification workshops are recommended to develop shared understanding. Automation and living documentation are presented as ways to prevent bugs. Quality is defined by how the software performs for users rather than bug counts. Measuring what matters to the business, rather than low level risks, is advised.
Agile Software Development for Non-Developers
A Crash Course Introduction into the world of Agile Software Development for people with a sparse or non-existent background in Software Development.
I held this presentation as a Brownbag session at ThoughtWorks Hamburg. The TDD part included a live coding session and the part about Continuous Integration and Continuous Delivery was backed with an example of a real Continuous Integration Server that worked on the results from the TDD live coding session.
Tdd
This document discusses test driven development (TDD). It begins by explaining the basic TDD process of writing a failing test, getting it to compile, making it pass without changing existing code, and then refactoring. It outlines some benefits of TDD like improved code quality and confidence in changes. It also notes some challenges like additional overhead and keeping test code clean. Overall, it argues that while TDD requires proper implementation, it can help produce higher quality code with fewer bugs.
Put to the Test
This document discusses refactoring code through careful modifications that do not change functionality. It emphasizes that refactoring requires rigorous unit testing to be done correctly. Successful refactoring can be achieved through uninterrupted work, pair programming, or test-driven development with an automated testing framework. Tests should be written early and often to catch errors introduced during refactoring. The minimum requirement for testing is assert statements, which provide an easy way to start testing without complex tools. Overall, the document stresses that refactoring is best approached as a disciplined process guided by thorough automated testing.
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
Stanly Lau is an agile coach and software developer based in Singapore who has worked with companies of various sizes in industries such as insurance, mobile safety, education, logistics, and banking. The document discusses legacy code and provides tips on how to deal with it. Legacy code is defined as code without unit tests that is difficult to change and prone to bugs. It recommends adopting modern engineering practices like test-driven development and refactoring. It also outlines an approach for identifying change points, breaking dependencies, writing tests, and then making changes to legacy code in a safe manner.
Check in dance
Introduction to Continuous Integration. Combining with Acceptance Test Driven Development, Test Driven Development, Showing how a developer in agile team does the work.
Introduction to Test Driven Development
This document provides an introduction to test-driven development (TDD), including its goals, benefits, and challenges. TDD is an iterative, test-first approach to development where functionality and behavior are defined by tests. Tests are written before code and define the desired API and design. Benefits of TDD include reduced defects, increased initial development time, and easier refactoring and collaboration. Adopting TDD requires practice and a focus on good design principles like separation of concerns.
TDD = bra design?
Test-drevet utvikling er en hellig gral innen smidig utvikling og ofte hører man uttrykk som "TDD fører til bra design", "med TDD trenger man ikke tenke på arkitektur" og "TDD er meningen med livet" (okei, det siste der fant jeg muligens på selv). Men vil TDD automatisk føre til bra design? Eller er det noe de ikke har fortalt deg?
A Not-So-Serious Introduction to Test Driven Development (TDD)
Most presentations I have seen on TDD is serious. Here is my not-so serious introduction to Test Driven Development (TDD). Enjoy.
Introducing EDD: Error Driven Development
This document discusses Error Driven Development (EDD) as an alternative to traditional Test Driven Development (TDD). EDD emphasizes reproducing bugs through tests before fixing them. It addresses common reasons teams avoid TDD, such as not making mistakes or tests taking too long, by arguing bugs will still occur and fixing them without tests is not faster. EDD aims to have teams focus on bugs by learning to reproduce them in tests in order to fix issues and avoid regressions.
Introduction to TDD (Test Driven development) - Ahmed Shreef
A short 20 minute introduction to Test Driven Development with simple example on unit testing using JUnit
Lập trình hướng kiểm thử - Test Driven development
This document discusses test driven development (TDD). It begins with an overview of TDD, explaining that TDD is a strong methodology that helps prevent bugs regardless of programming language. It then explains how to implement TDD using the "red/green/refactor" process in incremental baby steps. An example of reversing the last two characters of a string is provided. Benefits of TDD include clean code, preventing bugs, serving as documentation, and helping programmers design better. Common mistakes in TDD are also discussed. The document concludes with questions and answers about TDD.
Tdd practices
This document discusses test-driven development (TDD) practices. It covers the characteristics of good tests, what TDD is and why it is used, the TDD development cycle of red-green-refactor, best practices for TDD, anti-patterns to avoid, and practices for writing testable code. The key aspects of TDD outlined are writing tests before code, running tests after each small code change, and refactoring code between test cycles.
Best pratice
The document discusses several important topics for software development including unit testing, clean coding principles, design patterns, and useful development tools. It emphasizes that tests are important for preventing bugs and should be included in all projects. Clean coding principles like DRY, KISS and SRP help produce code that is easier to read, change and maintain. Design patterns provide solutions to common problems and a shared vocabulary for developers. Useful tools include IDEs, version control systems, code analysis tools and text editors which can help programmers work more efficiently if used properly.
TDD & Refactoring
The document discusses test-driven development (TDD) and refactoring. It explains what TDD is, how to implement it in three steps - writing a failing test, making the test pass, and refactoring code - and provides an example of modeling a calendar to track holidays using TDD. The document also discusses benefits of TDD like catching mistakes early, increasing coding confidence, and making it easier to implement new requirements through refactoring.
Guildford Coding Dojo1
The document introduces the Guildford Coding Dojo, which is a place for learning coding skills through deliberate practice, pair programming, and test-driven development (TDD). Attendees work on problems like FizzBuzz in timed pomodoro cycles, writing automated tests first before coding solutions and refactoring code with a focus on simple design. Rules include no distractions, practicing TDD and pair programming, and producing code that is well-tested, clear, and avoids duplication.
Tdd 4 everyone full version
This document discusses test-driven development (TDD) and its importance for software development. It notes that TDD is not just about unit testing code, but is a key part of software craftsmanship. When practicing TDD, tests should be written from the perspective of understanding by business analysts and customers, not just for code implementation. TDD promotes a short feedback loop to continually refine code through testing. Examples provided demonstrate how to use TDD for a FizzBuzz coding exercise by first writing tests to define requirements and then coding to pass those tests.
More Related Content
What's hot
Unit testing for project managers
This presentation gives you the evidence as to why unit testing works and a process for how to bring it your team as soon as possible. There's a reason why the growth of unit testing, and automated unit testing in particular, has exploded over the past few years. It not only improves your code, it's faster than releasing code without tests. You'll learn: What, exactly, is a unit test?; The 7 reasons why managers love unit testing; and how to change mindset and processes to start unit testing now.
TDD with RSpec
This document provides an introduction to unit testing with RSpec. It explains that unit tests check individual sections of code and integration tests check how those sections work together. It then describes the red-green-refactor process of test-driven development, where you first write a failing test, then pass the test with the simplest code, then refactor the code. Resources for learning more about RSpec and practicing tests are also provided.
Test Driven Development Part 1
TDD benefits
Clean Design
Fast Feedback
Concrete Evidence That Your Software Works
Write Better Code
Reduced Gold-Plating
Regression Test Suite
How To Do TDD
Analyze the requirements and write the list of tasks or features
Pick a task or feature
Brainstorm a list of tests for the task or feature
Review the tests list and pick a test
Write the test case
Run the test case and see it fails to compile
Write only enough code that the test case compiles
Run the test and see running the code fails
Write only enough code to just pass the test
Refactor the production code and eliminate duplication
Repeat
TDD and Getting Paid
Test-driven development is generally regarded as a good move: it should result in simple decoupled design, your tests tend to cover behaviour not methods, and far fewer bugs. However, just getting unit tests in on a real, commercial project is hard - switching to TDD is even harder. Often you can start a project with good intentions and coverage, then the deadline looms and the tests go out then the hacks come in. So, instead of beating ourselves up about not being perfect let's look at an interative approach to adopting TDD principles. We'll look at tactics for selling TDD to your client, boss and colleagues. This talk will also cover methods for making TDD easier for you by showing you what tools you can use to integrate it into your development environment. In the project itself, we'll examine how we can make small but permanent steps towards full TDD, without losing that progress when deadlines hit. We'll also cover a few methods for learning on your own time and how the whole process can actually be made quite enjoyable.
通往測試最高殿堂的旅程 - GTAC 2016
The Google Test Automation Conference (GTAC) is an annual test automation conference hosted by Google. 2016 is 10th GTAC. I'll share the most impressive parts of experience sharing & tool I heard in GTAC 2016 in this slide.
Why agile testing isn't working
The document discusses challenges with the traditional waterfall process and separating testing from development in Agile. It advocates for a whole team approach where testers and developers collaborate throughout the sprint. Specification workshops are recommended to develop shared understanding. Automation and living documentation are presented as ways to prevent bugs. Quality is defined by how the software performs for users rather than bug counts. Measuring what matters to the business, rather than low level risks, is advised.
Agile Software Development for Non-Developers
A Crash Course Introduction into the world of Agile Software Development for people with a sparse or non-existent background in Software Development.
I held this presentation as a Brownbag session at ThoughtWorks Hamburg. The TDD part included a live coding session and the part about Continuous Integration and Continuous Delivery was backed with an example of a real Continuous Integration Server that worked on the results from the TDD live coding session.
Tdd
This document discusses test driven development (TDD). It begins by explaining the basic TDD process of writing a failing test, getting it to compile, making it pass without changing existing code, and then refactoring. It outlines some benefits of TDD like improved code quality and confidence in changes. It also notes some challenges like additional overhead and keeping test code clean. Overall, it argues that while TDD requires proper implementation, it can help produce higher quality code with fewer bugs.
Put to the Test
This document discusses refactoring code through careful modifications that do not change functionality. It emphasizes that refactoring requires rigorous unit testing to be done correctly. Successful refactoring can be achieved through uninterrupted work, pair programming, or test-driven development with an automated testing framework. Tests should be written early and often to catch errors introduced during refactoring. The minimum requirement for testing is assert statements, which provide an easy way to start testing without complex tools. Overall, the document stresses that refactoring is best approached as a disciplined process guided by thorough automated testing.
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
Stanly Lau is an agile coach and software developer based in Singapore who has worked with companies of various sizes in industries such as insurance, mobile safety, education, logistics, and banking. The document discusses legacy code and provides tips on how to deal with it. Legacy code is defined as code without unit tests that is difficult to change and prone to bugs. It recommends adopting modern engineering practices like test-driven development and refactoring. It also outlines an approach for identifying change points, breaking dependencies, writing tests, and then making changes to legacy code in a safe manner.
Check in dance
Introduction to Continuous Integration. Combining with Acceptance Test Driven Development, Test Driven Development, Showing how a developer in agile team does the work.
Introduction to Test Driven Development
This document provides an introduction to test-driven development (TDD), including its goals, benefits, and challenges. TDD is an iterative, test-first approach to development where functionality and behavior are defined by tests. Tests are written before code and define the desired API and design. Benefits of TDD include reduced defects, increased initial development time, and easier refactoring and collaboration. Adopting TDD requires practice and a focus on good design principles like separation of concerns.
TDD = bra design?
Test-drevet utvikling er en hellig gral innen smidig utvikling og ofte hører man uttrykk som "TDD fører til bra design", "med TDD trenger man ikke tenke på arkitektur" og "TDD er meningen med livet" (okei, det siste der fant jeg muligens på selv). Men vil TDD automatisk føre til bra design? Eller er det noe de ikke har fortalt deg?
A Not-So-Serious Introduction to Test Driven Development (TDD)
Most presentations I have seen on TDD is serious. Here is my not-so serious introduction to Test Driven Development (TDD). Enjoy.
Introducing EDD: Error Driven Development
This document discusses Error Driven Development (EDD) as an alternative to traditional Test Driven Development (TDD). EDD emphasizes reproducing bugs through tests before fixing them. It addresses common reasons teams avoid TDD, such as not making mistakes or tests taking too long, by arguing bugs will still occur and fixing them without tests is not faster. EDD aims to have teams focus on bugs by learning to reproduce them in tests in order to fix issues and avoid regressions.
Introduction to TDD (Test Driven development) - Ahmed Shreef
A short 20 minute introduction to Test Driven Development with simple example on unit testing using JUnit
Lập trình hướng kiểm thử - Test Driven development
This document discusses test driven development (TDD). It begins with an overview of TDD, explaining that TDD is a strong methodology that helps prevent bugs regardless of programming language. It then explains how to implement TDD using the "red/green/refactor" process in incremental baby steps. An example of reversing the last two characters of a string is provided. Benefits of TDD include clean code, preventing bugs, serving as documentation, and helping programmers design better. Common mistakes in TDD are also discussed. The document concludes with questions and answers about TDD.
Tdd practices
This document discusses test-driven development (TDD) practices. It covers the characteristics of good tests, what TDD is and why it is used, the TDD development cycle of red-green-refactor, best practices for TDD, anti-patterns to avoid, and practices for writing testable code. The key aspects of TDD outlined are writing tests before code, running tests after each small code change, and refactoring code between test cycles.
Best pratice
The document discusses several important topics for software development including unit testing, clean coding principles, design patterns, and useful development tools. It emphasizes that tests are important for preventing bugs and should be included in all projects. Clean coding principles like DRY, KISS and SRP help produce code that is easier to read, change and maintain. Design patterns provide solutions to common problems and a shared vocabulary for developers. Useful tools include IDEs, version control systems, code analysis tools and text editors which can help programmers work more efficiently if used properly.
TDD & Refactoring
The document discusses test-driven development (TDD) and refactoring. It explains what TDD is, how to implement it in three steps - writing a failing test, making the test pass, and refactoring code - and provides an example of modeling a calendar to track holidays using TDD. The document also discusses benefits of TDD like catching mistakes early, increasing coding confidence, and making it easier to implement new requirements through refactoring.
What's hot (20)
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
A Not-So-Serious Introduction to Test Driven Development (TDD)
A Not-So-Serious Introduction to Test Driven Development (TDD)
Introduction to TDD (Test Driven development) - Ahmed Shreef
Introduction to TDD (Test Driven development) - Ahmed Shreef
Lập trình hướng kiểm thử - Test Driven development
Lập trình hướng kiểm thử - Test Driven development
Similar to Kata de TDD by Jordi Anguela
Guildford Coding Dojo1
The document introduces the Guildford Coding Dojo, which is a place for learning coding skills through deliberate practice, pair programming, and test-driven development (TDD). Attendees work on problems like FizzBuzz in timed pomodoro cycles, writing automated tests first before coding solutions and refactoring code with a focus on simple design. Rules include no distractions, practicing TDD and pair programming, and producing code that is well-tested, clear, and avoids duplication.
Tdd 4 everyone full version
This document discusses test-driven development (TDD) and its importance for software development. It notes that TDD is not just about unit testing code, but is a key part of software craftsmanship. When practicing TDD, tests should be written from the perspective of understanding by business analysts and customers, not just for code implementation. TDD promotes a short feedback loop to continually refine code through testing. Examples provided demonstrate how to use TDD for a FizzBuzz coding exercise by first writing tests to define requirements and then coding to pass those tests.
TDD BDD PHP - Sviluppo guidato dai test in PHP con phpspec
Phpspec è uno strumento che può aiutarci a scrivere codice pulito e funzionante facilitandoci nell'adottare delle pratiche di Behaviour-Driven Development (BDD). Ma cos’è il BDD? Qual è la differenza tra il BDD e il Test-Driven Development (TDD)? Quali sono le differenze tra le famiglie di tool xSpec e xUnit? Quali strumenti mette a disposizione l’ecosistema PHP per praticare il TDD?
Pair programming and introduction to TDD
These are slides used in a workshop on TDD. Slides explain more about different types of pair programming techniques when to use each, what is TDD and how to start thinking about TDD as mindset change.
Introducción práctica a Test-Driven Development (TDD)
The document introduces test-driven development (TDD) and provides an overview of its key concepts and practices. TDD combines test-first development and refactoring, using automated tests as a design tool. It describes the basic TDD cycle of writing a failing test, making it pass with the minimum code, and refactoring. Benefits include breaking work into small chunks, avoiding over-engineering, and encouraging loose coupling. Techniques like fake it till you make it and triangulation are presented, along with examples of practicing TDD on a FizzBuzz kata. The importance of practice and learning from experience is emphasized.
Introducción práctica a TDD
Slides usadas en la primera sesión de la comunidad Software Craftsmanship Alicante para introducir Test Driven Development
TDD - Unit testing done right and programmer happiness
Test Driven Development has been around for a while but it has been dismissed by many as a superfluous and tedious way of developing software.
I have discovered through experience that it helps me create better quality code while turning the development into an even more enjoyable process.
In this talk I explain what makes it so great, tackle some of the criticism and share some tips regarding better unit testing.
Global Day of Coderetreat Munich 2017
The document describes a Global Day of CodeRetreat event taking place in Munich on November 18, 2017. The event involves 2000 developers from 100 cities and 6 continents pairing up to work through 6 sessions of test-driven development (TDD) exercises over 1 day using 1 kata (problem). Each session involves switching pairing partners and introduces constraints to challenge participants, such as writing tests first, continuous integration/refactoring, object-oriented principles, and functional programming techniques. The goal is for developers to learn and improve their TDD and software design skills in a low-pressure environment away from their day jobs.
TDD for the masses
Slides of my talk at the Cmd+U Conference with live coding. The code can be found here: http://bit.ly/TDD-CmdU
TDD Walkthrough - The Time in Words
This document summarizes a TDD walkthrough for converting times to words. It begins by setting up the necessary files and frameworks. The first test case converts 5:00 to "five o' clock" and fails initially. Code is then written to pass this test. Additional tests are added for other times like 5:30 and 5:15, with code changes to pass each new test while maintaining previous tests. Refactoring removes duplication, leading to cleaner code structure using variables and objects. The walkthrough demonstrates a step-by-step TDD process.
TDD - Test Driven Development - Java JUnit FizzBuzz
A short example Test Driven Development session where I code FizzBuzz.
FizzBuzz is often used as a programming interview question and as a Kata for practicing your coding.
The GitHub code repository with the Java code for this exercise is available at:
https://github.com/eviltester/fizzbuzz
Read the blog post for the video:
http://blog.eviltester.com/2018/03/tdd-test-driven-development-java-junit.html
JavaScript frontend testing from failure to good to great
TDD for DOM code is challenging but possible. The presenter demonstrated a simple example of TDD for jQuery code using Jasmine that broke code into small testable modules, isolated dependencies, and allowed for changes with confidence through an integrated CI process and headless test running. Frontend TDD, while difficult, results in code that is better tested and maintained.
TDD Flow: The Mantra in Action
San Francisco Software Craftsmanship Meetup
Test Driven Developers Bay Area Meetup
TDD Flow: The Mantra in Action” is a talk + hands-on about the mantra of TDD and its core patterns. Here are some questions for this talk: What is TDD? How to write a good test that fails? How to write code enough to make the test pass? How to remove duplication? How to refactor code? How to create clean code? Is TDD about testing or design? How small should a test be? Should I only write unit tests? Should I estimate TDD? How to use TDD with other agile methods like Scrum, Kanban or BDD? And finally, how to flow in TDD?
TDD reloaded - JUGTAA 24 Ottobre 2012
Seconda serata di introduzione al Test-Driven Development, tenuta in XPeppers a Trento il 24 Ottobre 2012.
Nelle slide c'è anche la descrizione del coding dojo sullo string calculator che abbiamo svolto assieme.
Test Driven Development Workshop
This presentation was used for a workshop on Test Driven Development, using the Fizz Buzz Coding Dojo Kata.
Test-Driven Development
This document summarizes notes from Kent Beck's book "TDD by Example" on test-driven development (TDD). It outlines the core principles of TDD, including writing tests first before code and eliminating duplication. It also describes techniques like red-green-refactor cycles where tests are written to fail initially ("red"), made to pass ("green"), and then code is refactored. The document provides examples of applying TDD to a money conversion problem and discusses patterns for testing, refactoring, and overcoming fears that arise during the process.
TDD and Simple Design Workshop - Session 1 - March 2019
The document discusses test-driven development (TDD) and simple design. It introduces TDD and some of its core practices, including test-driven development, simple design, refactoring, and pair programming. It provides an agenda for a workshop that will cover these topics over three sessions, including extreme programming (XP), the four elements of simple design, test doubles, outside-in TDD, and SOLID principles. The workshop aims to communicate best practices for using technical practices to succeed with agile development.
Lean Responsive
Build better web and mobile experiences faster by building and testing only what you need on any device.
Unwritten Manual for Pair Programming
This document discusses pair programming and provides guidance on how to effectively implement it. It begins by explaining the purpose of pair programming is to produce high quality software. It then discusses various pairing techniques like ping-pong pairing and mob programming. The document also identifies benefits like higher quality code and faster defect removal, as well as challenges like being tiring. Finally, it provides tips for making pairing work well such as starting with a defined task, switching roles frequently, and not forcing people who strongly dislike pairing.
Test Driven Development
The document introduces Test Driven Development (TDD). TDD is a software development process that relies on short development cycles where you write an automated test first, then code to pass that test, and refactor as needed. The key benefits of TDD are that it encourages simple design, validates correctness, and drives the design of a program in a modular way. TDD best practices include writing self-explanatory test assertions, keeping tests small and isolated, integrating code frequently, and following the TDD mantra and rhythm of red-green-refactor.
Similar to Kata de TDD by Jordi Anguela (20)
TDD BDD PHP - Sviluppo guidato dai test in PHP con phpspec
TDD BDD PHP - Sviluppo guidato dai test in PHP con phpspec
Introducción práctica a Test-Driven Development (TDD)
Introducción práctica a Test-Driven Development (TDD)
TDD - Unit testing done right and programmer happiness
TDD - Unit testing done right and programmer happiness
TDD - Test Driven Development - Java JUnit FizzBuzz
TDD - Test Driven Development - Java JUnit FizzBuzz
JavaScript frontend testing from failure to good to great
JavaScript frontend testing from failure to good to great
TDD and Simple Design Workshop - Session 1 - March 2019
TDD and Simple Design Workshop - Session 1 - March 2019
More from Codium
Lean code kata en PHPMad
Kata hecha el 23 de enero de 2019 en el grupo PHPMad donde pusimos en práctica cómo ir entregando valor de forma iterativa.
Desarrollando a velocidad de crucero - CAS 2018
Los proyectos suelen empezar con un ritmo de desarrollo muy rápido. A medida que maduran van perdiendo velocidad hasta que llega a un punto en que el coste y tiempo de añadir funcionalidad es extremadamente elevado.
En esta charla @luisrovirosa nos habla, desde un punto de vista técnico, cómo podemos diseñar y desarrollar el producto para aportar valor al final de cada sprint. Para ello muestra ejemplos de cómo hemos simplificado un producto y las prácticas que hemos utilizado para mantener la velocidad de desarrollo y la deuda técnica bajo control. También hablaremos del coste de cada una de ellas.
Algunas de las técnicas son el vertical slicing, simplificar, test driven development, refactoring y automatización de la infraestructura.
Learned lessons in real world projects by Jordi Anguela at Mallorca Software ...
En esta charla hablé de:
- cómo gestionamos un nuevo proyecto,
- automatizamos el setup con Docker,
- utilizamos los pipelines de Bitbucket para ejecutar los tests automáticamente
- de cómo encapsulamos el dominio del proyecto con DDD.
- y garantizamos la calidad y el correcto funcionamiento con TDD,
La charla se enfoca desde un punto práctico, con ejemplos y mostrando aquellas partes que más problemas nos han dado y las soluciones que planteamos.
Charla impartida en @scmallorca: https://www.meetup.com/Mallorca-Software-Craftsmanship/events/247679413/
Learned lessons in a real world project by Luis Rovirosa at PHPMad
En esta charla hablé de:
- cómo gestionamos un nuevo proyecto,
- automatizamos el setup con Docker,
- utilizamos los pipelines de Bitbucket para ejecutar los tests automáticamente
- de cómo encapsulamos el dominio del proyecto con DDD.
- y garantizamos la calidad y el correcto funcionamiento con TDD,
La charla se enfoca desde un punto práctico, con ejemplos y mostrando aquellas partes que más problemas nos han dado y las soluciones que planteamos.
Charla impartida en @phpmad en https://www.meetup.com/es-ES/PHPMad/events/246861723/
Learned lessons in a real world project
This document summarizes lessons learned from a 2-month project with 2 part-time developers. It discusses automating infrastructure with Docker and Docker Compose, ensuring quality with testing practices like TDD and acceptance tests, and keeping the domain model at the heart of the project using DDD principles. Automation provides easy setup and updates but must be double checked. TDD allows for refactoring and simplifies code. DDD simplifies communication but increases complexity. Going deeper requires a focus on software craftsmanship.
Slow life
Vivimos en una sociedad acelerada, donde las rutinas y la inercia del día a día hacen que no seamos dueños de nuestras vidas.
Aunque no acabemos de estar satisfechos con nuestro trabajo, el miedo al cambio, al rechazo y al fracaso hacen que no tomemos ninguna acción para mejorar nuestra situación.
Ir más lentos, aprender a decir a ‘no’ y deshacernos de lo que no nos aporta nos ha permitido disfrutar con nuestra profesión, tener claro nuestras prioridades, compaginar la vida profesional con la personal, conseguir mejores clientes y desarrollar proyectos de forma sostenible.
En esta charla compartiremos cómo hemos ralentizado nuestro ritmo para ser más conscientes de nuestras necesidades, tomar mejores decisiones y ser felices.
Charla impartida en Software Craftsmanship Barcelona 2017
More from Codium (6)
Learned lessons in real world projects by Jordi Anguela at Mallorca Software ...
Learned lessons in real world projects by Jordi Anguela at Mallorca Software ...
Learned lessons in a real world project by Luis Rovirosa at PHPMad
Learned lessons in a real world project by Luis Rovirosa at PHPMad
Recently uploaded
一比一原版(sdsu毕业证书)圣地亚哥州立大学毕业证如何办理
原版一模一样【微信：741003700 】【(sdsu毕业证书)圣地亚哥州立大学毕业证成绩单】【微信：741003700 】学位证，留信认证（真实可查，永久存档）原件一模一样纸张工艺/offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原。
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
【主营项目】
一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！
二.真实使馆公证(即留学回国人员证明,不成功不收费)
三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）
四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度)
如果您处于以下几种情况：
◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】
◇面对父母的压力，希望尽快拿到；
◇不清楚认证流程以及材料该如何准备；
◇回国时间很长，忘记办理；
◇回国马上就要找工作，办给用人单位看；
◇企事业单位必须要求办理的
◇需要报考公务员、购买免税车、落转户口
◇申请留学生创业基金
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】外观非常简单，由纸质材料制成，上面印有校徽、校名、毕业生姓名、专业等信息。
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】格式相对统一，各专业都有相应的模板。通常包括以下部分：
校徽：象征着学校的荣誉和传承。
校名:学校英文全称
授予学位：本部分将注明获得的具体学位名称。
毕业生姓名：这是最重要的信息之一，标志着该证书是由特定人员获得的。
颁发日期：这是毕业正式生效的时间，也代表着毕业生学业的结束。
其他信息：根据不同的专业和学位，可能会有一些特定的信息或章节。
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】价值很高，需要妥善保管。一般来说，应放置在安全、干燥、防潮的地方，避免长时间暴露在阳光下。如需使用，最好使用复印件而不是原件，以免丢失。
综上所述，办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】是证明身份和学历的高价值文件。外观简单庄重，格式统一，包括重要的个人信息和发布日期。对持有人来说，妥善保管是非常重要的。
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
Building API data products on top of your real-time data infrastructure
This talk and live demonstration will examine how Confluent and Gravitee.io integrate to unlock value from streaming data through API products.
You will learn how data owners and API providers can document, secure data products on top of Confluent brokers, including schema validation, topic routing and message filtering.
You will also see how data and API consumers can discover and subscribe to products in a developer portal, as well as how they can integrate with Confluent topics through protocols like REST, Websockets, Server-sent Events and Webhooks.
Whether you want to monetize your real-time data, enable new integrations with partners, or provide self-service access to topics through various protocols, this webinar is for you!
Cost-Effective Strategies For iOS App Development
In this infographic, we have explored cost-effective strategies for iOS app development, focusing on building high-quality apps within a budget. Key points covered include prioritizing essential features, leveraging existing tools and libraries, adopting cross-platform development approaches, optimizing for a Minimum Viable Product (MVP), and integrating with cloud services and third-party APIs. By implementing these strategies, businesses and developers can create functional and engaging iOS apps while minimizing development costs and time-to-market.
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Ensuring Efficiency and Speed with Practical Solutions for Clinical Operations
Clinical operations professionals encounter unique challenges. Balancing regulatory requirements, tight timelines, and the need for cross-functional collaboration can create significant internal pressures. Our upcoming webinar will introduce key strategies and tools to streamline and enhance clinical development processes, helping you overcome these challenges.
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Ensuring the optimal performance of your audio-visual (AV) equipment is crucial for delivering exceptional experiences. AV performance validation is a critical process that verifies the quality and functionality of your AV setup. Whether you're a content creator, a business conducting webinars, or a homeowner creating a home theater, validating your AV performance is essential.
How GenAI Can Improve Supplier Performance Management.pdf
Data Collection and Analysis with GenAI enables organizations to gather, analyze, and visualize vast amounts of supplier data, identifying key performance indicators and trends. Predictive analytics forecast future supplier performance, mitigating risks and seizing opportunities. Supplier segmentation allows for tailored management strategies, optimizing resource allocation. Automated scorecards and reporting provide real-time insights, enhancing transparency and tracking progress. Collaboration is fostered through GenAI-powered platforms, driving continuous improvement. NLP analyzes unstructured feedback, uncovering deeper insights into supplier relationships. Simulation and scenario planning tools anticipate supply chain disruptions, supporting informed decision-making. Integration with existing systems enhances data accuracy and consistency. McKinsey estimates GenAI could deliver $2.6 trillion to $4.4 trillion in economic benefits annually across industries, revolutionizing procurement processes and delivering significant ROI.
Software Test Automation - A Comprehensive Guide on Automated Testing.pdf
Moving to a more digitally focused era, the importance of software is rapidly increasing. Software tools are crucial for upgrading life standards, enhancing business prospects, and making a smart world. The smooth and fail-proof functioning of the software is very critical, as a large number of people are dependent on them.
Best Practices & Tips for a Successful Odoo ERP Implementation
Implementing Odoo, a robust and all-inclusive business management software, can significantly improve your organisation. To get the most out of it and ensure a smooth implementation, it is important to have a strategic plan. This blog shares some essential tips to help you with successful Odoo ERP implementation. From planning and customisation to training and support, this blog outlines some expert advice that will guide you through the process confidently. It is true that adopting a new software can be challenging, and hence, this post has tailored these tips to help you avoid common mistakes and achieve the best results. Whether you run a small business or a large enterprise, these tips will help you streamline operations, boost productivity, and drive growth. Whether you are new to Odoo or looking to improve your current setup, it is essential to learn the key strategies for a successful Odoo implementation. Implementing Odoo doesn’t have to be difficult. With the right approach and guidance, you can use this software to elevate your business. Read on to discover the secrets of a successful Odoo implementation.
Why is successful Odoo implementation crucial?
Implementing Odoo effectively can transform your business by making processes smoother, increasing efficiency, and providing useful insights. It helps align your operations with best practices, boosting productivity and aiding better decision-making. A well-executed implementation ensures you get the most out of your investment, while a poor one can cause disruptions, higher costs, and frustration among employees.
TheFutureIsDynamic-BoxLang-CFCamp2024.pdf
Just like life, our code must adapt to the ever changing world we live in. From one day coding for the web, to the next for our tablets or APIs or for running serverless applications. Multi-runtime development is the future of coding, the future is to be dynamic. Let us introduce you to BoxLang.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
42 Ways to Generate Real Estate Leads - Sellxpert
Generate hot real estate leads with these simple strategies. 42 innovative ways to attract clients in the real estate industry.
ACE - Team 24 Wrapup event at ahmedabad.
Atlassian Team 24 event wrap-up Ahmedabad. Recap of Atlassian team24 event.
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...Ortus Solutions, Corp
Join us for a session exploring CommandBox 6’s smooth website transition and efficient deployment. CommandBox revolutionizes web development, simplifying tasks across Linux, Windows, and Mac platforms. Gain insights and practical tips to enhance your development workflow.
Come join us for an enlightening session where we delve into the smooth transition of current websites and the efficient deployment of new ones using CommandBox 6. CommandBox has revolutionized web development, consistently introducing user-friendly enhancements that catalyze progress in the field. During this presentation, we’ll explore CommandBox’s rich history and showcase its unmatched capabilities within the realm of ColdFusion, covering both major variations.
The journey of CommandBox has been one of continuous innovation, constantly pushing boundaries to simplify and optimize development processes. Regardless of whether you’re working on Linux, Windows, or Mac platforms, CommandBox empowers developers to streamline tasks with unparalleled ease.
In our session, we’ll illustrate the simple process of transitioning existing websites to CommandBox 6, highlighting its intuitive features and seamless integration. Moreover, we’ll unveil the potential for effortlessly deploying multiple websites, demonstrating CommandBox’s versatility and adaptability.
Join us on this journey through the evolution of web development, guided by the transformative power of CommandBox 6. Gain invaluable insights, practical tips, and firsthand experiences that will enhance your development workflow and embolden your projects.Hands-on with Apache Druid: Installation & Data Ingestion Steps
Supercharge your analytics workflow with https://bityl.co/Qcuk Apache Druid's real-time capabilities and seamless Kafka integration. Learn about it in just 14 steps.
Upturn India Technologies - Web development company in Nashik
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
Recently uploaded (20)
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Building API data products on top of your real-time data infrastructure
Building API data products on top of your real-time data infrastructure
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Call Girls Bangalore🔥7023059433🔥Best Profile Escorts in Bangalore Available 24/7
Ensuring Efficiency and Speed with Practical Solutions for Clinical Operations
Ensuring Efficiency and Speed with Practical Solutions for Clinical Operations
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
How GenAI Can Improve Supplier Performance Management.pdf
How GenAI Can Improve Supplier Performance Management.pdf
Software Test Automation - A Comprehensive Guide on Automated Testing.pdf
Software Test Automation - A Comprehensive Guide on Automated Testing.pdf
Best Practices & Tips for a Successful Odoo ERP Implementation
Best Practices & Tips for a Successful Odoo ERP Implementation
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...
Strengthening Web Development with CommandBox 6: Seamless Transition and Scal...
Hands-on with Apache Druid: Installation & Data Ingestion Steps
Hands-on with Apache Druid: Installation & Data Ingestion Steps
Upturn India Technologies - Web development company in Nashik
Upturn India Technologies - Web development company in Nashik
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Kata de TDD by Jordi Anguela
- 1. Kata de TDD Jordi Anguela 31th May 2018@tgndevs @etseURV
- 2. Built 2 startups and Codium +10 years doing web applications +5 years training teams In startups and corporations About me
- 3. Audience First meet-up? Who usually writes automated tests? Anyone using TDD?
- 4. Agenda Small theoretical introduction - 20min FizzBuzz kata in pairs - 1h Final discussion - 20min Free drink at the bar - after the session
- 7. Cheap
- 9. Cost of fixing bugs
- 10. Fast
- 11. Eliminate waste Do only what you need now. Simple solutions
- 12. Cost of fear change
- 13. Better
- 15. Unit testing Integration testing Types of testing Internal quality External quality Acceptance tests
- 16. Test pyramid
- 18. Example of unit testing
- 19. TDD flow
- 20. TDD Never add functionality without a failing test Never refactor with a failing test Baby steps
- 22. Kata FizzBuzz Write a program that returns the numbers from 1 to 100. But for multiples of three returns "Fizz" instead of the number. For the multiples of five returns "Buzz". For the multiples of fifteen returns "FizzBuzz". 1 2 Fizz 4 Buzz Fizz 7 8 Fizz Buzz 11 Fizz 13 14 FizzBuzz 16 17 Fizz 19 Buzz ... etc up to 100
- 23. Kata: FizzBuzz github.com/codiumteam Java, C#, PHP and JS
- 24. Kata FizzBuzz Write a program that returns the numbers from 1 to 100. But for multiples of three returns "Fizz" instead of the number. For the multiples of five returns "Buzz". For the multiples of fifteen returns "FizzBuzz". 1 2 Fizz 4 Buzz Fizz 7 8 Fizz Buzz 11 Fizz 13 14 FizzBuzz 16 17 Fizz 19 Buzz ... etc up to 100 A number is Fizz if it has a 3 in it A number is Buzz if it has a 5 in it A number is FizzBuzz if it has a 3 in it it has a 5 in it The previous requirements are still correct.
- 25. Summary Never add functionality without a failing test Never refactor with a failing test Baby steps
- 26. Thank you Jordi Anguela jordianguela @CodiumTeam #tddcodium
- 27. How to transition into TDD TDD slows you down at the beginning Don’t get stuck writing tests Start writing 1 test (at least) per feature Applying TDD to legacy code is hard Refactor carefully Apply TDD only the new parts of code Choose a project that doesn’t have a short deadline Hire knowledge