By default, Invoke-Pester runs all *.Tests.ps1 files in the local directory and its subdirectories. That’s a useful default, but the parameters of Invoke-Pester let you control the alternatives.<\/p>\n
\nSee the posts in this Pester series:<\/p>\n To run all *.Tests.ps1 files in a particular directory or collection of directories, use the Script<\/b> parameter. The Script<\/b> parameter of Invoke-Pester was originally named Path<\/b>, but it does so many things that they had to come up with a more generic name for it.<\/p>\n When you use the Script<\/b> parameter of Invoke-Pester and give it paths to one or more directories, Invoke-Pester runs all .Tests.ps1 files in all subdirectories of the directories recursively. This is terrific for testing modules and other projects in progress. It supports wildcard characters, too.<\/p>\n For example, this command runs all *.Tests.ps1 files in the two specified directories and their subdirectories.<\/p>\n But, you can tell it to run other types of files.<\/p>\n To direct Invoke-Pester to run any file, enter the path and file name in the value of the Script<\/b> parameter. For example, this command tells Invoke-Pester to run the elusively named Test-ScriptWithPesterTest.ps1 file.<\/p>\n Invoke-Pester runs the files that you specify as the value of the Script parameter, just as though you ran them at the command line, including code that is not part of the Pester test.<\/p>\n You can even use Invoke-Pester to run PowerShell scripts that contain no tests, like my PowerShell profile. It dutifully reports that no tests passed or failed.<\/p>\n Be sure to include the file name of non-.Tests.ps1 files. If you use a wildcard, Invoke-Pester reverts to its default, which runs only the .Tests.ps1 files (recursively).<\/p>\n You can specify both directories and files. Again, if you specify a directory, Invoke-Pester runs only the .Tests.ps1 files in the directory (recursively).<\/p>\n And, you can specify a particular .Tests.ps1 file, too.<\/p>\n But, you can also select tests within files<\/p>\n To run only certain tests within the files specified by the Script<\/b> parameter, use the TestName, Tag<\/b>, and ExcludeTag<\/b> parameters of Invoke-Pester. These parameters filter within the files specified by the paths in the Script parameter; they never expand its range.<\/p>\n The TestName<\/b> parameter runs only Describe blocks with the specified test names or name patterns. It is case-insensitive. Remember that TestName<\/b> looks only at names of Describe blocks, even though the InModuleScope, Context, and It blocks have required names.<\/p>\n For example, this command runs only the Describe blocks with names that include “parameter.”<\/p>\n If you specify multiple TestName values, Invoke-Pester runs tests that have any of the values in the Describe name (it ORs the values).<\/p>\n The Tag<\/b> and ExcludeTag<\/b> parameters run Describe blocks that have the specified tags, that is, the values of the Tag parameter of the Describe function. They are case-insensitive, but they don’t support wildcard characters. And, at least in Pester 3.4.0, they cannot find tags that include spaces. So they find “UnitTest,” but cannot find “Unit Test,” even if its an exact match for a tag.<\/p>\n When you specify multiple tags, Invoke-Pester runs tests that have any of the listed tags (it ORs the tags).<\/p>\n But, when you use the TestName<\/b> and Tag<\/b> parameters in the same command (at least in version 3.4.0), Invoke-Pester combines the requirements and runs only the tests that have the specified TestName and Tag (it ANDs the requirements).<\/p>\n Predictably, the ExcludeTag parameter runs all Describe blocks except for those that match any of the Tag values. If a test is included by the Tag parameter and excluded by the ExcludeTag parameter, ExcludeTag takes precedence over Tag, and the test does not run.<\/p>\n Interestingly, tests that are filtered out by TestName<\/b>, Tag<\/b>, and ExcludeTag<\/b> are not counted as skipped. Only tests that have the Skip<\/b> parameter of the It function are listed in the Skip count value.<\/p>\n For example, there are multiple tests in the file, but only one has the NullTest tag. Notice that the Skipped value is 0.<\/p>\n That’s pretty high-resolution control. Next, we’ll talk about passing parameters to a Pester test script.<\/p>\n <\/p>\n Learning Pester? Check out Real-World Test-Driven Development with Pester<\/a>. The code and slides are in Github at https:\/\/github.com\/juneb\/PesterTDD<\/a>.<\/p>\n June Blender is a technology evangelist at SAPIEN Technologies, Inc. and a Windows PowerShell MVP. You can reach her at <\/em>juneb@sapien.com <\/em><\/a>or follow her on Twitter at <\/em>@juneb_get_help<\/em><\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Applies to: Pester 3.4.0 In How to Run Pester Tests, I talked about the different places that you can put your Pester days and the different ways to run them, including, but not limited to, the Invoke-Pester function. Today, I’ll talk about the parameters of Invoke-Pester function that let you determine which tests run. Next, […]<\/p>\n","protected":false},"author":31,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1122,1119,1121,25],"tags":[1127,934,1123,28],"class_list":["post-12201","post","type-post","status-publish","format-standard","hentry","category-behavior-driven-development-bdd","category-pester","category-test-driven-development","category-windows-powershell","tag-invoke-pester","tag-juneb","tag-pester","tag-powershell"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/12201","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/31"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=12201"}],"version-history":[{"count":18,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/12201\/revisions"}],"predecessor-version":[{"id":12503,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/12201\/revisions\/12503"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=12201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=12201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=12201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"clip_image002\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2016\/06\/clip_image002_thumb-1.jpg\" "\\"clip_image002\\"")
<\/a><\/p>\n\n
\nRun all Tests.ps1 files in a path<\/h1>\n
Invoke-Pester -Script C:\\GitHub\\MyProject, D:\\Working\\*\\1.0<\/pre>\n
Run tests in other files<\/h1>\n
Invoke-Pester -Script C:\\GitHub\\MyProject\\Test-ScriptWithPesterTest.ps1<\/pre>\n
PS C:\\> Invoke-Pester C:\\Users\\JuneB\\Documents\\WindowsPowerShell\\profile.ps1\r\n\r\nTests completed in 0ms\r\nPassed: 0 Failed: 0 Skipped: 0 Pending: 0 Inconclusive: 0<\/pre>\n
Invoke-Pester -Script C:\\GitHub\\MyProject\\*.ps1 # Runs only .Tests.ps1 files<\/pre>\n
Invoke-Pester -Script C:\\GitHub\\MyProject\\Project.ps1, D:\\Working\\*\\1.0<\/pre>\n
Invoke-Pester -Script C:\\GitHub\\MyProject\\Project.ps1, C:\\Scripts\\Module.Help.Tests.ps1<\/pre>\n
Run Selected Pester Tests<\/h1>\n
Invoke-Pester C:\\Scripts\\Module.Help.Tests.ps1 -TestName '*parameter*'\r\n\r\n#In file\r\nDescribe \"gets parameter descriptions\" {...} # runs this one\r\nDescribe \"gets correct types of parameters\" {...} # runs this one, too\r\nDescribe \"gets mandatory\" { It \"parameter is mandatory\" {...}...} # doesn't run this one\r\n<\/pre>\nInvoke-Pester C:\\Scripts\\Module.Help.Tests.ps1 -TestName '*correct*', \"*mandatory*\"\r\n\r\n#In file\r\nDescribe \"gets parameter descriptions\" {...} # doesn't run this one\r\nDescribe \"gets correct parameter types\" {...} # runs this one\r\nDescribe \"gets mandatory\" { It \"parameter is mandatory\" {...}...} # runs this one\r\n<\/pre>\nInvoke-Pester C:\\Scripts\\Module.Help.Tests.ps1 -Tag UnitTest, 'Unit test'\r\n\r\n#In file\r\nDescribe \"finds the synopsis\" -Tag UnitTest {...} #Runs this test\r\nDescribe \"finds the return value\" -Tag 'Unit Test' {...} #Doesn't run this test\r\n<\/pre>\nInvoke-Pester C:\\Scripts\\Module.Help.Tests.ps1 -Tag Unit, Regression\r\n\r\n#In file\r\nDescribe \"gets parameter descriptions\" -Tag Unit {...} # Runs this test\r\nDescribe \"gets mandatory value\" -Tag regression {...} # Runs this test\r\nDescribe \"gets correct parameter types\" {...} # Doesn't run this test\r\n<\/pre>\nInvoke-Pester C:\\Scripts\\Module.Help.Tests.ps1 -TestName '*parameter*' -Tag UnitTest\r\n\r\n#In file\r\nDescribe \"gets parameter descriptions\" -Tag UnitTest {...} # Runs this test\r\nDescribe \"gets correct parameter types\" {...} # Doesn't run this test\r\nDescribe \"gets mandatory value\" -Tag UnitTest {...} # Doesn't run this test\r\n<\/pre>\nPS C:\\ > C:\\Scripts\\Module.Help.Tests.ps1 -TestName '*parameter*' -Tag NullTest\r\n\r\nDescribing gets parameter descriptions\r\n\r\n[+] parameter description is not null 42ms\r\nTests completed in 0ms\r\n\r\nPassed: 1 Failed: 0 Skipped: 0 Pending: 0 Inconclusive: 0\r\n<\/pre>\n