From 8fc68cab0dd1ea3ec66c87b631be9fe52ed3a4f2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aleksandar=20Nikoli=C4=87?= Date: Fri, 5 Aug 2016 17:14:51 +0200 Subject: [PATCH] Update testing-guidelines.md --- docs/testing-guidelines/testing-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/testing-guidelines/testing-guidelines.md b/docs/testing-guidelines/testing-guidelines.md index 10d75da4f5..4fc516a42e 100755 --- a/docs/testing-guidelines/testing-guidelines.md +++ b/docs/testing-guidelines/testing-guidelines.md @@ -101,7 +101,7 @@ If these tests find regressions, you'll be notified that your PR is not ready, a We have taken a functional approach to the layout of our Pester tests. You should place new tests in their appropriate location. If you are making a fix to a cmdlet in a module, the test belongs in the module directory. -If you are unsure; you can make it part of your PR, or create an issue. +If you are unsure, you can make it part of your PR, or create an issue. The current layout of tests is: * test/powershell/engine * test/powershell/engine/Api