Skip to content
Hallway
0:00 / 0:00

#tdd#unittesting#test-drivendevelopment

TDD Revisited - Ian Cooper - NDC London 2021

NDC Conferences

230K subscribers • 110 videos on Hallway • Conference channel

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Ian Cooper
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

15K views5 years ago2 recommendations

Tools and practiceSoftware designTestingSoftware architectureDesign patterns

Ian Cooper explores common fallacies of Test-Driven Development and shares pragmatic principles for writing effective unit tests.

In this talk we will look at the key Fallacies of Test-Driven Development, such as 'Developers write Unit Tests', or 'Test After is as effective as Test First' and explore a set of Principles that let us write good unit tests instead. Attendees should be able to take away a clear set of guidelines as to how they should be approaching TDD to be successful. The session is intended to be pragmatic advice on how to follow the ideas outlined in my 2013 talk "TDD Where Did it All Go Wrong"

Why it's here

2 people recommend this

What people say. Recommended as a pragmatic guide to understanding and successfully implementing Test-Driven Development.

u/flavius-asin r/softwarearchitecture • Recommends

On “Hexagonal and Onion architecture”

https://herbertograca.com/2017/11/16/explicit-architecture-01-ddd-hexagonal-onion-clean-cqrs-how-i-put-it-all-together/ link to this video link to this video Go through these 3 in order. Stop for a few days reading others, and just synthesize in your mind what you read/listened. Then go again through them in the same order. And then, only then, go here link to this video Additionally to keep in mind: * DDD is what you do inside the domain model. It's an implementation detail of the domain model * you can add also vertical slicing into the mix. Beware: slices are supposed to be big, not every little thing is supposed to get its own slice. The way I identify slices is by talking to the business people and identifying th…
7View on Reddit

u/voroninpin r/dotnet • Recommends

On “Unit testing, how many of you are actually doing it.”

First and foremost: unit != class. link to this video Second Sometimes snapshot testing is a time saver. Give it a chance maybe. See GitHub.com/VerifyTests/Verify Third. Some tools you may like some hate. Try and decide what fits you. FluentAsserions, NSubstitute, Moq, Autofixture,, Bogus, FsCheck, LightBDD, Stryker.NET, Test containers, dotnet watch test, live unit testing. You can even try writing tests in F# and be surprised how concise they can be. I also expect more convenience with source generators and interceptors (.net 8 feature). Fourth. Writing good maintainable unit tests is extremely hard. I cannot say I've mastered the skill. I recommend investing time in reading several books about…
1View on Reddit