
.NET Testing Techniques You Didn’t Know You Needed - Dante De Ruwe - NDC Oslo 2026
Keywords
Summary
176 words
Critical Evaluation
Value of the Information & Strength of the Argument
The talk offers substantial practical value by addressing common pain points in software testing with actionable techniques. The argumentation is solid, grounded in real-world experience and concrete code examples. De Ruwe effectively demonstrates the rationale behind each technique, such as using randomized testing to avoid human bias and property-based testing to go beyond example-based assertions. He also provides clear reasoning for managing flaky tests through determinism and sample size. The use of anecdotes, like the energy management smart meter incident, strengthens the argument. However, the talk is more applied than theoretical, and some claims lack formal evidence, but within the scope of a practitioner talk, the value is high.
Scientific Rigor, Source Quality, Title Accuracy
The scientific rigor is moderate; the talk is based on accepted software engineering practices but does not cite external studies or formal sources. The libraries mentioned (Bogus, FsCheck) are well-known in the .NET ecosystem, and the techniques described are grounded in established testing theory. The speaker references a prior NDC talk on property-based testing but does not provide its URL. The title perfectly matches the content, as the talk indeed presents lesser-known testing techniques. The description only includes general conference links, which are not directly related to the technical content, but that is typical for conference recordings. Overall, the information is reliable from a practitioner standpoint, though not peer-reviewed.
233 words
Title / Content Match
The title accurately reflects the content, as the talk indeed introduces less-known testing techniques such as mutation, property-based, and snapshot testing.
Quality & Reliability
7/10
The talk is a well-structured practitioner-oriented presentation covering established testing techniques with concrete examples and war stories, but lacks rigorous scientific validation and citations.
Key Moments
Markers derived by PSI from the transcript: the creator did not define chapters.
- Introduction and audience interaction: who considers themselves a developer and cares about testing.
- Reasons to test: preventing bugs, documenting behavior, fast feedback, regression prevention, and trust.
- Decision tree for test failures: broken code, incomplete tests, and flaky tests.
- Randomized testing with an alphanumeric filter example and the Bogus library.
- Flaky test issue due to daylight saving time and the energy smart meter war story.
- Property-based testing introduction and the FsCheck library.
- Mars rover kata to illustrate how to find properties of code.
- Strategies for dealing with flaky tests: deterministic seeding, large sample sizes, and test repeatability.
Cited Sources
- NDC Conferences — Official conference website mentioned in the description.
- NDC Oslo — Specific conference event where the talk was recorded.
Contribution & Novelties
The talk provides a synthesis of several advanced testing techniques, making them accessible to a broader audience. It offers practical advice on implementing mutation testing, property-based testing, and snapshot testing in .NET, with a focus on improving test effectiveness and reliability. The discussion on flaky tests, including causes and solutions, is particularly valuable. The novel contribution lies in the clear explanation of how to identify and apply these techniques in real-world scenarios.
Pour aller plus loin :
- Property-based testing — Overview of the technique and its principles.
- Mutation testing — Explanation of how mutation testing works and its benefits.
- Snapshot testing (without URL) — Concept of capturing output to detect unintended changes, often used in frontend and API testing.
119 words
Radar Profile
The radar profile shows a strong orientation toward technical depth and practical application, with high scores in quantity of information and technical level, while the reliability and generic quality are moderate, indicating a talk rich in actionable content but not formally corroborated.