Test Driven Development (TDD) - Beginners Essentials course

Simpliv

Course

Online

£ 50 VAT inc.

The best Other Education courses

See all

See all

Description

  • Type

    Course

  • Methodology

    Online

  • Start date

    Different dates available

This Test Driven Development course for beginners of any language will show you the right overview to embrace TDD, Unit tests and refactor.Hi there, my name is Ignacio Paz. I am an Agile coach, I was a professor in the university for 15 years for Systems Design and Agile methodologies. I applied Test driven development heavily while working as Java Architect for many years.I was originally fascinated with Test Driven Development back in the year 2009, at that time I learnt all the key knowledge and I designed a TDD course that I improved over the years and delivered to hundreds of students. I am really excited to be able to bring this course online for all of you!Are you looking to give the first right steps with Test Driven development? This course will teach the concepts of TDD in the right way along with its true philosophy before you move to a course with coding. We will see key concepts in depth for unit tests, emergent design, refactoring, test doubles, mocks and stubs.This course is for beginners in TDD but it is recommended that you have some previous knowledge in any programming language and understand concepts of object oriented programming. You will start right from the beginning and work our way through step by step.The course has the examples in Java but the concepts can be applied to any language. The code examples are all explained and easy to read by any programmer of other languages like PHP, Python, .Net and more.If you have never used unit test or you have already tried junit and are struggling with the basics of unit tests and TDD, this course is for you and together we will learn the right mindset to work with Test driven development.

Facilities

Location

Start date

Online

Start date

Different dates availableEnrolment now open

About this course

Test driven development
Refactoring
Code smells
TDD
Anti patterns
SOLID
Design principles
Mocks
Stubs
Emergent design
Unit Test

Questions & Answers

Add your question

Our advisors and other users will be able to reply to you

Who would you like to address this question to?

Fill in your details to get a reply

We will only publish your name and question

Emagister S.L. (data controller) will process your data to carry out promotional activities (via email and/or phone), publish reviews, or manage incidents. You can learn about your rights and manage your preferences in the privacy policy.

Reviews

This centre's achievements

2021

All courses are up to date

The average rating is higher than 3.7

More than 50 reviews in the last 12 months

This centre has featured on Emagister for 6 years

Subjects

  • Benefits
  • Object oriented training
  • Testing
  • Java
  • Object-oriented training
  • Object-oriented software
  • Approach
  • Design
  • Project
  • Programming

Course programme

Unit Tests 3 lectures 12:47 What is a Unit Test? This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have Unit Test Example We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
Good Unit Tests: FIRST This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
Unit Tests Quiz Unit Tests 3 lectures 12:47 What is a Unit Test? This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have Unit Test Example We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
Good Unit Tests: FIRST This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
Unit Tests Quiz What is a Unit Test? This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have What is a Unit Test? This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have What is a Unit Test? This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have What is a Unit Test? This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have This Lecture is to learn what a unit test is We cover the following topics: · Unit of work · xUnit · How all these components work together and the benefits of working with unit tests. · Outcomes of a unit test · Benefits of unit tests · How many unit test a project should have Unit Test Example We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
Unit Test Example We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
Unit Test Example We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
Unit Test Example We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
We go through a unit test example based on a Sale class. We add a test for the getChange Method.
  • Example of a Unit test
  • Name of unit test classes
  • Sections of a unit test: The 3As - Arrange, Act, Assert
Good Unit Tests: FIRST This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
Good Unit Tests: FIRST This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
Good Unit Tests: FIRST This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
Good Unit Tests: FIRST This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
This lecture is about the characteristics of a good unit test described by the acronym FIRST.
  • Levels of Testing
  • Good Unit Tests: First
  • Fast, Independent, Repeatable, Self-Validating, Thorough
Unit Tests Quiz Unit Tests Quiz Unit Tests Quiz Unit Tests Quiz Refactoring 3 lectures 15:27 Design upfront and Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design Refactoring - What to refactor? We cover what refactor is a related concepts.
  • Refactoring Book by Martin Fowler: debt
  • Refactoring: Improve the code without changing the functionality
  • Code smells: For more take a look at For more take a look at Refactoring - How to refactor? We look at the techniques to refactor.
    • Design Principles
    • Don’t repeat yourself
    • Advices from Gang of four. From book Design Patterns: Elements of Reusable Object-Oriented Software principle
    • SOLID principles: Find code examples in the following links.
    • Single Responsibility Principle Close Principle Substitution Principle(LSP) Segregation Principle (ISP) Inversion Principle of main Refactoring techniques. For more and code examples, please take a look of unit tests as a safety net for refactoring
    Refactoring Quiz Refactoring. 3 lectures 15:27 Design upfront and Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design Refactoring - What to refactor? We cover what refactor is a related concepts.
    • Refactoring Book by Martin Fowler: debt
    • Refactoring: Improve the code without changing the functionality
    • Code smells: For more take a look at For more take a look at Refactoring - How to refactor? We look at the techniques to refactor.
      • Design Principles
      • Don’t repeat yourself
      • Advices from Gang of four. From book Design Patterns: Elements of Reusable Object-Oriented Software principle
      • SOLID principles: Find code examples in the following links.
      • Single Responsibility Principle Close Principle Substitution Principle(LSP) Segregation Principle (ISP) Inversion Principle of main Refactoring techniques. For more and code examples, please take a look of unit tests as a safety net for refactoring
      Refactoring Quiz Design upfront and Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design Design upfront and Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design Design upfront and Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design Design upfront and Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design We compare the difference between designing the system upfront vs an approach of an emergent design in contexts where change is inevitable · Design Upfront · Change is inevitable · Emergent Design Refactoring - What to refactor? We cover what refactor is a related concepts.
      • Refactoring Book by Martin Fowler: debt
      • Refactoring: Improve the code without changing the functionality
      • Code smells: For more take a look at For more take a look at Refactoring - What to refactor? We cover what refactor is a related concepts.
        • Refactoring Book by Martin Fowler: debt
        • Refactoring: Improve the code without changing the functionality
        • Code smells: For more take a look at For more take a look at Refactoring - What to refactor? We cover what refactor is a related concepts.
          • Refactoring Book by Martin Fowler: debt
          • Refactoring: Improve the code without changing the functionality
          • Code smells: For more take a look at For more take a look at Refactoring - What to refactor? We cover what refactor is a related concepts.
            • Refactoring Book by Martin Fowler: debt
            • Refactoring: Improve the code without changing the functionality
            • Code smells: For more take a look at For more take a look at cover what refactor is a related concepts.
              • Refactoring Book by Martin Fowler: debt
              • Refactoring: Improve the code without changing the functionality
              • Code smells: For more take a look at For more take a look at cover what refactor is a related concepts.
                • Refactoring Book by Martin Fowler: debt
                • Refactoring: Improve the code without changing the functionality
                • Code smells: For more take a look at For more take a look at Refactoring - How to refactor? We look at the techniques to refactor.
                  • Design Principles
                  • Don’t repeat yourself
                  • Advices from Gang of four. From book Design Patterns: Elements of Reusable Object-Oriented Software principle
                  • SOLID principles: Find code examples in the following links.
                  • Single Responsibility Principle Close Principle Substitution Principle(LSP) Segregation Principle (ISP) Inversion Principle of main Refactoring techniques. For more and code examples, please take a look of unit tests as a safety net for refactoring
                  Refactoring - How to refactor? We look at the techniques to refactor.
                  • Design Principles
                  • Don’t repeat yourself
                  • Advices from Gang of four. From book Design Patterns: Elements of Reusable Object-Oriented Software principle
                  • SOLID principles: Find code examples in the following links.
                  • Single Responsibility Principle Close Principle Substitution Principle(LSP) Segregation Principle (ISP) Inversion Principle of main Refactoring techniques. For more and code examples, please take a look of unit tests as a safety net for refactoring
                  Refactoring - How to refactor? We look at the techniques to refactor.
                  • Design Principles
                  • Don’t repeat yourself
                  • Advices from Gang of four. From book Design Patterns: Elements of Reusable Object-Oriented Software principle
                  • SOLID principles: Find code examples in the following links.
                  • Single Responsibility Principle Close Principle Substitution Principle(LSP) Segregation Principle (ISP) Inversion Principle of main Refactoring techniques. For more and code examples, please take a look of unit tests as a safety net for refactoring
                  Refactoring - How to refactor? We look at the techniques to refactor.
                  • Design Principles
                  • Don’t repeat yourself
                  • Advices from Gang of four. From book Design Patterns: Elements of Reusable Object-Oriented Software principle
                  • SOLID principles: Find code examples in the following links.
                  • Single Responsibility Principle Close Principle Substitution Principle(LSP) Segregation Principle (ISP) Inversion Principle of main Refactoring techniques. For more and code examples, please take a look of unit tests as a safety net for refactoring
                  We look at the techniques to refactor.
                  • Design Principles
                  • Don’t repeat yourself
                  • Advices from Gang of four. From book Design Patterns: Elements of Reusable Object-Oriented Software principle
                  • SOLID principles: Find code examples in the following links.
                  • Single Responsibility Principle Close Principle Substitution Principle(LSP) Segregation Principle (ISP) Inversion Principle of main Refactoring techniques count...

Additional information

Knowledge of some programming language The examples are in Java but they are explained and anyone with programming skills should be able to understand them

See related categories

Test Driven Development (TDD) - Beginners Essentials course

£ 50 VAT inc.

The best Other Education courses

See all

See all