TDD in real life

TL;DR

This content provides an overview of TDD and demonstrates how to implement it in goal through live coding examples.

Transcript

interesting bug from restream which didn't allow us to share the coding part the best part but Adelina almost managed yeah let's try let's try together next time next time we'll bring a board and a pen yeah I decided that so if you know if you joined late or you know I'll go through it quickly um but um I wanna you will see my slides in the their f... Read More

Key Insights

• 🔍 Test-driven development (TDD) is the focus of the content provided.
• 💻 The content includes live coding demonstrations of TDD in Golang.
• 📚 The author highlights the importance of understanding the language in order to write good tests.
• 🔑 Engineers should take ownership of testing their product at all levels, not just unit tests.
• 🧱 Practicing TDD can help with organizing work and keeping code simple.
• ✅ The pros of TDD include increased confidence in code changes and new functionality.
• 🔄 Red-Green-Refactor is a popular approach to writing tests in TDD.
• 🌐 Integration tests are a valuable way to test the compatibility and integration of multiple components.

Questions & Answers

Q: What are the four core principles of TDD highlighted in the content?

The four core principles of TDD are: thorough understanding of the language, taking ownership of testing at all levels, considering functional and non-functional tests, and using TDD to help organize work and keep it simple.

Q: Why are unit tests called the most numerous in the testing pyramid?

Unit tests are called the most numerous because they focus on testing individual units of code, such as functions or methods, and are typically the most granular level of testing.

Q: What is the red-green-refactor method and how can it be used in testing at different levels?

The red-green-refactor method involves starting with a failing test, writing just enough code to make the test pass, and then considering any necessary refactoring. It can be used to write tests at any level, whether it's unit tests, integration tests, or end-to-end tests.

Q: Why is it important to test outputs rather than implementations in TDD?

Testing outputs instead of implementations helps avoid writing brittle tests and minimizes the need for maintenance and refactoring. By focusing on inputs and outputs and expected behavior, tests remain more robust and less tied to specific implementation details.

Q: What is contract testing, and how does it differ from end-to-end testing?

Contract testing involves testing the integration between two services by using a contract and creating mocks. It focuses on ensuring that two services work well together without having to run the full application. In contrast, end-to-end testing involves testing the entire stack and is typically slower and more expensive.

Summary & Key Takeaways

• The speaker introduces the core principles of TDD in goal, emphasizing the importance of understanding the language and taking ownership of testing.

• The red-green-refactor method is explained as a way to write tests at any level, and the testing pyramid is introduced as a guide for test coverage.

• The speaker highlights the pros and cons of TDD, such as increased confidence in code changes and writing tests that focus on inputs and outputs.