folderrefa.blogg.se

Modifications to items created in parent blocks are not reversed, see caution below.

When exiting a block, files and folders created during it's lifetime will be removed.

All files and folders created by your setups and tests are available during the lifetime of that block, including inner blocks.

A clean TestDrive is created per container (test-file or scriptblock) on entry to the first top-level block (Describe or Context) in that container.

Scoping īasic scoping rules are implemented for the TestDrive: I highly encourage you to explore the module source on github.

You may use this drive to isolate the file operations of your test to a temporary store. It doesn’t come with Pester tests Instead, use the Test-Equality cmdlet from the Functional module on PowerShell Gallery. Pester will remove this drive after the tests completes. Pester also supports testing of string values, as demonstrated in Test Group 4. Pester creates a PSDrive inside the user's temporary drive that is accessible via a named PSDrive TestDrive. It is usually desirable not to perform file activity tests that will produce side effects outside of an individual test. Why should I care That’s a more involved question if you’re new to DevOps in general. It provides a language that allows you to define test cases, and the Invoke-Pester cmdlet to execute these tests and report the results.

TestDrive is a PowerShell PSDrive for file activity limited to the scope of a block ( Describe or Context).Ī test may need to work with file operations and validate certain types of file activities. What is Pester That’s easy to answer Pester is a test framework for PowerShell. Isolating File Operations using the TestDrive