Building a Testable Data Access Layer
•Als PPT, PDF herunterladen•
6 gefällt mir•8,015 views
All developers understand the theoretical value of unit testing, but with data driven applications, figuring out how to create tests can be hard. In this session, you will learn how to design and build a data layer that can be tested. We will introduce data layer architecture practices and methodologies that make testing possible, and cover the basics of unit test mocking. You will also be guided through various types of testing, including unit, integration, and functional testing. Leave this session with the basics needed to start creating tests for application data layers, including those powered by LinqToSQL and Entity Framework.
![Introductions ,[object Object],[object Object],[object Object],[object Object],[object Object],@toddanglin TelerikWatch.com](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Ähnlich wie Building a Testable Data Access Layer
Ähnlich wie Building a Testable Data Access Layer (20)
Mehr von Todd Anglin
Mehr von Todd Anglin (17)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Building a Testable Data Access Layer
- 1. Building a Testable Data Access Layer Todd Anglin Chief Evangelist, Telerik Level: Intermediate
- 3. today’s plan
- 4. what is a “data layer”?
- 6. why build a data layer? what’s the benefit?
- 8. Presentation Web Desktop Domain Logic (“the code that makes you money”) Data Persistence Database Cloud XML Etc. Service
- 9. a good data layer…
- 11. a bad data layer is…
- 13. how do we build “data layers”?
- 19. testing the data layer
- 32. should you test your DAL?
Hinweis der Redaktion
- Visual Studio Live Orlando 2010MGB 2003 © 2003 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
- Easy = Easy to build if you’re not careful
- Everything is familiar up to this point. Now the dreaded step may of us avoid: Creating tests for the data layer
- Hides issues example = concurrency, auto-gen DB values, etc.