0:00 / 0:00
#cleanarchitecture#integrationtesting#.netcore
Clean Testing: Clean Architecture with .NET Core
SSW TV | Videos for developers, by developers
38K subscribers • 2 videos on Hallway
- Recommended by 1 person: 1 in engineering communities.
- Presented by Jason Taylor
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
42K views6 years ago1 recommendation
Software designTools and practiceSoftware architectureTestingDesign patterns
Jason Taylor explains how to apply Clean Architecture principles to write clean, independent integration tests in .NET Core.
Clean Testing - Clean Architecture with .NET Core by Jason Taylor || Subscribe for more content from SSW TV || || Press like and leave a comment below to let us know how we're doing || - Introduction - The Basics of Clean Architecture - Clean Testing - Testing Tools - Live Demos: Create Your Own Application - Recommendations And Resources - Final Summary Twitter ↴ twitter.com/ssw_tv Facebook ↴ facebook.com/SSW.page ------------------------------------------------------------------------------ All developers should be writing automated tests. In fact modern developers should be doing Clean Testing. Systems that adhere to the principles of Clean Architecture are independent of UIs, databases, frameworks, and other external concerns. As a result, the domain and business logic, the most important parts of the system, are completely isolated from external concerns. This makes writing automated tests, a whole lot easier. In this talk, join Jason Taylor from SSW as he uncovers a simplified approach to automated testing with Clean Architecture. You will learn about unit tests, integration tests, and subcutaneous tests, along with tools, frameworks, and most importantly, where to focus your efforts. You leave this talk fully prepared to implement your own simplified approach to automated testing with Clean Architecture. ABOUT THE PRESENTER Jason Taylor is a solution architect, trainer, mentor, and full stack developer with 20 years professional experience. Currently specializing in teaching and building enterprise applications utilizing .NET Core, Angular, Vue, and Azure. Jason loves a challenge and is skilled at progressing from a simple proposal into a well-defined, coded, and tested solution. Jason loves public speaking and has run the .NET Core Superpowers to sold out audiences in Sydney, Brisbane and Melbourne. Give Jason your feedback! ↴ forms.microsoft.com/Pages/ResponsePage.aspx?id=NHwvrDW56Uir3… ------------------------------------------------------------------------------ Created by SSW TV | Videos By Developers, For Developers See more at tv.ssw.com For any production related enquiries please email || info@ssw.com.au ||Why it's here
1 person recommends thisWhat people say. Recommended for its insights into structuring integration tests using static classes in Clean Architecture.
Moments people linked to
u/zaibufin r/dotnet • Mentions
Can someone explain how using static on class level works?
I've been following both Jimmy Bogard and Jason Taylor and what I've noticed in their integration tests is that they use a using static Testing on their test classes. This gives access to the defined Testing class without having to pass it as a Fixture or create a new instance.
Normally a using statement means you dispose it after it's done. Is the Testing class disposed for each test class that's using it?
Example here https://github.com/jasontaylordev/CleanArchitecture/blob/main/tests/Application.IntegrationTests/TodoItems/Commands/CreateTodoItemTests.cs
[video