From aacf97708e8e8b736593931acccef63c14c8b5c7 Mon Sep 17 00:00:00 2001 From: Emma L Garland Date: Wed, 18 Oct 2023 10:49:37 +0100 Subject: [PATCH] Update unit-testing.md v10 --- 10/umbraco-cms/implementation/unit-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10/umbraco-cms/implementation/unit-testing.md b/10/umbraco-cms/implementation/unit-testing.md index 5b88f302c41..397d8852c95 100644 --- a/10/umbraco-cms/implementation/unit-testing.md +++ b/10/umbraco-cms/implementation/unit-testing.md @@ -5,7 +5,7 @@ description: A guide to getting started with unit testing in Umbraco # Unit Testing Umbraco -These examples inspire unit testing in Umbraco with Umbraco 9.x and 10.x, using [NUnit](https://nunit.org/), [Moq](https://github.com/moq/moq4), and [AutoFixture](https://github.com/AutoFixture/AutoFixture). There are many ways of testing Umbraco and there’s no right or wrong way. +These examples inspire unit testing in Umbraco with Umbraco 9.x, 10.x, 11.x and 12.x, using [NUnit](https://nunit.org/), [Moq](https://github.com/moq/moq4), and [AutoFixture](https://github.com/AutoFixture/AutoFixture). There are many ways of testing Umbraco and there’s no right or wrong way. When testing components in Umbraco, such as controllers, helpers, services etc. these components often require that you provide a couple of dependencies in your classes using [dependency injection](../reference/using-ioc.md). This is because a lot of magic happens “under the hood” of Umbraco and these dependencies are needed for that magic to happen.