Unit TestingSecrets of an Umbraco Ninja

Presented by:

Aaron Powellme@aaron-powell.com

@slace www.aaron-powell.com

• Not Test Driven Development• Separation of logic from UI• Ability to create reusable components• Reduced errors by repeatable tests in

controlled environments• Better API design

What and Why?

Umbraco UI

Code

Build

Deploy

Test

Umbraco

Logic

UITests

Code

Test

BuildDeploy

Test

• Stub is an instance which wont break your test– Stubs can be implementations of a class

created purely for testing purposes• Mocks– Less common in current unit testing– Type instances where nothing is defined– Can be very brittle

Stub & Mocks

• Do you need a mocking framework?– Short answer is no– Can create your own stub types– Gives you greater control

• Why to use one?– Easy expectation setup– Using stubs on less accessible types

• Set-less properties

Frameworks

• WebForms MVP to abstract away ASP.NET WebForms features

• Dependency Injection to simplify the creation of factory types

• Factory Pattern for data access

Development

• Heavy reliance of HttpContext– Hard to Mock– Requires a web context

• Lots of static– Hard to mock

• Changing data– What are we working against?

With Umbraco

Ninja Coding!

Questions?Thank you for coming