awesome-talkscurated list on GitHubRecommends
Under “Test-Driven Development”
TDD: Theme & Variations by **Kent Beck** (Tech Excellence 2024) 57:29
0:00 / 0:00
TDD: Theme & Variations (Kent Beck)
Tech Excellence
6.1K subscribers • 2 videos on Hallway
- Recommended by 2 people: 1 in engineering communities and 1 curated list.
- Presented by Kent Beck, author of Test-Driven Development: By Example
Intermediate. Assumes working knowledge.
17K views1 year ago2 recommendations
Software designTools and practiceTestingDesign patternsSoftware architecture
Kent Beck explores the history, core practices, and modern variations of test-driven development, including TCR, mocks, and scope management.
Test-driven development (TDD) has become a polarizing development practice. Claims about TDD range from “absurd” to “essential” to “damaging” to “joyous.” In this talk, we’ll take a step back and look at TDD in context, including its history, current practice, and potential future. Outline of the session: - History of TDD - Canon TDD - Variations: TCR, Exploratory, Mocks, Top-down, Bottom-up, Unit vs integration, Up-front - Effects of TDD - anxiety, scope management, defect density, trust, responsibility ABOUT KENT Kent Beck is the rediscoverer of TDD, author of 9 books on programming including “Test-Driven Development: By Example”, and current artist & musician. - LinkedIn: linkedin.com/in/kentbeck/ - Twitter: twitter.com/KentBeck - GitHub: github.com/KentBeck - Website: kentbeck.com/ - Substack: substack.com/@kentbeck TECH EXCELLENCE - Subscribe to our YouTube channel youtube.com/@TechExcellence - Join our Meetup Group meetup.com/techexcellence - Follow us on LinkedIn linkedin.com/company/techexcellenceio - Follow us on Twitter twitter.com/techexcellence_ - Join our Discord Community discord.gg/KXdf4t4j2m #testdrivendevelopment #tdd #continuousdelivery #techexcellenceWhy it's here
2 people recommend thisWhat people say. Recommended as an insightful overview of TDD history and variations by its pioneer, helping developers understand unit versus integration testing.
Moments people linked to
u/SideburnsOfDoomin r/dotnet • Recommends
On “How do you best prepare for writing solid unit and integration tests in C#?”
> What resources would you recommend? Are there any go-to tutorials, articles, books, or courses that really helped you grasp unit and integration testing with xUnit and Moq?
Kent Beck
Ian Cooper
But basically, if "use moq" is a key part of your testing strategy, I already know that your results might be ok, but won't ever be great. See the Kent Beck video about here. Look into the Test Host.
u/SideburnsOfDoomin r/dotnet • Recommends
On “Is anyone out there choosing to avoid DI in their .NET projects?”
> It does not give any name to tests that are larger that can reasonably be called unit tests, but don't use external software and therefore would not run into the running time/ performance issue.
Those are "unit tests". Your metric of "too large" just isn't even relevant.
The queston is, are they _good_ unit tests. Maybe, maybe they're too large.
Close-coupled, mock-heavy class-method tests can - and very often be terrible unit tests too.
If you want links on ths topic, then
link to this video
https://www.artofunittesting.com/definition-of-a-unit-test
u/SideburnsOfDoomin r/dotnet • Recommends
On “How do you best prepare for writing solid unit and integration tests in C#?”
>I am still testing the integration between the web server, logic layers, and data access layers.
You seem to be using the meaning of "integration" of "multiple classes in the same test".
I get that many people use that meaning.
The one problem is, that it is not historically accurate, see the link above - "integration" is used once only, with reference to tests that "are about the integration of your code with that other software". Other software such as a database or http web service is integration.
On the other hand, is "a unit test tests a class, a test with multiple classes is integration" a useful definition that leads to good tests today? Again, no it is not. "A test should be se…