[hemmerling] Scripting Languages for Windows 3/3 - Testing with Windows PowerShell

Related page:

• Scripting Programming Languages for Windows 1/3.
• Scripting Programming Languages for Windows 2/3 - Windows PowerShell.

• Start-Automating - “A software services company”.
  • YouTube Channel "StartAutomating".
  • The OpenSource Start-Automating "ScriptCop" - “A module to help make sure your PowerShell scripts are following the rules”.
    • GitHub "StartAutomating/ScriptCop".
    • Microsoft Technet "ScriptCop".
    • There is also a free online PowerShell code checking service ScriptCop.
• Example script.
  • GitHub "StartAutomating/ScriptCop/blob/master/Tests/ScriptCoverage.Test.ps1".
• Documentation.
  • GitHub.
    • GitHub "StartAutomating/ScriptCop/tree/master/en-us".
  • Online.
    • Start-Automating "ScriptCop" - "A Quick Intro To ScriptCop".
    • Start-Automating "ScriptCop" - "About ScriptCop Rules".
    • Start-Automating "ScriptCop" - "ScriptCop About Scriptcop Fixers".

• Microsoft TechNet Blog "Hey, Scripting Guy! Blog. Learn about Windows PowerShell" - "Use ScriptCop to Help Write Better PowerShell Scripts".

• GitHub "mbergal/Jester".
• NuGet "Jester".
• LinkedIn "Misha Bergal", Facebook "Misha Bergal", Twitter "Misha Bergal, @mbergal", Google+ "Misha Bergal", VK "Misha Bergal", YouTube "Misha Bergal".
• Though not suggested by the author in his example code, Jester may be installed in the Powershell module directory.
• Installation:
  • Installation by NuGet:
    1. Download “Jester” to your local directory by “NuGet install Jester”.
    2. Copy the directory “Jester.0.0.1” to the PowerShell module directory
    3. Rename the directory “Jester.0.0.1” it to “Jester”.
  • Installation by GitHub:
    1. Download the archive “Jester-master.zip” from GitHub to a local directory.
    2. Unzip the archive “Jester-master.zip”, so that the directory “Jester-master” is created.
    3. Copy the directory “Jester-master\src” to the PowerShell module directory.
    4. Rename the directory “src” it to “Jester”.
  • Last step of Installation: Add to “Microsoft.PowerShellISE_profile.ps1”:

Set-ExecutionPolicy Unrestricted
Set-ExecutionPolicy Bypass
Unblock-File C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\Jester\*.ps1
Import-Module Jester

• GitHub "knutkj/PSTest".
  • GitHub "knutkj/PSTest/downloads" - Download of Windows installers of the software.
  • GitHub Wiki "knutkj/PSTest".
  • GitHub Wiki "knutkj/PSTest" - "PsTest NuGet package".
• LinkedIn "Knut Kristian Johansen", Facebook "Knut Kristian Johansen", YouTube "Knut Kristian Johansen".
• Blog Knut Kristian Johansen’s blog. Bits and pieces from my professional life.
  • Knut Kristian Johansen’s blog "How to do NUnit assertions with PowerShell" - Instructions how to install NUnit and how to creat the 2 files “NUnit.psd1” and “NUnit.psm1”.
• NuGet "PsTest".
  • You may download “PSTest” to your local directory with the “Package Manager Console” by 'PM>“NuGet install PSTest”'.
• Installation:
  • Installation by NuGet:
    1. Download “PSTest” to your local directory by “NuGet install PSTest”.
    2. Copy the directory “PsTest.1.0.4654.251\tools” to the PowerShell module directory
    3. Rename the directory “tools” it to “PSTest”.
  • Installation by GitHub:
    1. Download the archive “PSTest-master.zip” from GitHub to a local directory.
    2. Unzip the archive “PSTest-master.zip”, so that the directory “PSTest-master” is created.
    3. Copy the directory “PSTest-master\PsTest\bin\Debug” to the PowerShell module directory.
    4. Rename the directory “Debug” it to “PSTest”.
    5. Copy the directory “PSTest-master\PsTest\*.ps1” to the PowerShell module subdirectory “PSTest”.
  • Installation of NUnit.
    1. Download and unzip “NUnit-2.6.4.zip” from github.com/nunit/nunitv2/releases.
    2. Create a Powerscript module subdirectory “NUnit”. Copy the file “NUnit-2.6.4\bin\framework\nunit.framework.dll” from the unzipped download to that directory.
    3. Create the 2 files “NUnit.psd1” and “NUnit.psm1” in the module subdirectory, according to Knut Kristian Johansen’s blog "How to do NUnit assertions with PowerShell".
    4. On Win8 with .NET 4.5 framework, the DLL “nunit.framework.dll” is still blocked ( “Properties - “This file came from another computer and might be blocked to help protect this computer” ). Unblock the DLL file ( “Properties / Unblock” )! Unblocking can't be undone?!

• Scott Hanselman "Testing PowerShell scripts with NUnit".
• Elegant Code "Integration Test Brought to you by Powershell & NUnit – with a Little Specification Syntax for Flavoring".

• GitHub "pester/Pester", NuGet "Pester" - “PowerShell BDD style testing framework”.
  • Wiki GitHub Wiki "pester/Pester".
• GitHub "dfinke/IsePester" - “Module to integrate PowerShell Pester into ISE”.

• Installation:
  • Installation by NuGet:
    1. Download “Pester.3.3.9” to your local directory by “NuGet install Pester”.
    2. Copy the directory “tools” to the PowerShell module directory
    3. Rename the directory “tools” it to “Pester”.
  • Installation by GitHub:
    1. Download the archive “Pester-master.zip” from GitHub to a local directory.
    2. Unzip the archive “Pester-master.zip”, so that the directory “Pester-master” is created.
    3. Copy the directory “Pester-master” to the PowerShell module directory.
    4. Rename the directory “Pester-master” it to “Pester”.
  • Last step of installation: Add to “Microsoft.PowerShellISE_profile.ps1”:

Set-ExecutionPolicy Unrestricted
Set-ExecutionPolicy Bypass
Unblock-File C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\Pester\Functions\*.ps1
Unblock-File C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\Pester\Functions\Assertions\*.ps1 
Import-Module Pester

• PSUnit, CodePlex "PSUnit", GitHub "tellingmachine/PSUnit".
• Twitter "psunit, @psunit" ( - 2011-09-20 ).
• CodePlex Wiki "PSUnit" - Documentation.
• LinkedIn "Klaus Graefensteiner", Twitter "Klaus Graefensteiner, @senf", Google+ "Klaus Graefensteiner", YouTube "Klaus Graefensteiner", Microsoft MSDN - Channel9 "Klaus Graefensteiner"
• Blog Klaus Graefensteiner "Tellingmachine - Vom Hundersten ins Tausende".
  • Tellingmachine "The very first PSUnit Pilot is testing the PowerShell |e| Tie-Fighter aka Get-Enumerator Cmdlet", 2009-07 - Unit Tests Example.
  • Tellingmachine "PSUnit PowerShell Unit Testing Framework - Getting Started Guide - Installation - Version 2 Beta 1", 2009-08 - Installation Guide.
  • Tellingmachine "PSUnit PowerShell Unit Testing Framework - Getting Started Guide - Writing Unit Tests - Version 2 Beta 1", 2009-08 - Writing Unit Tests.
  • Tellingmachine "PSUnit PowerShell Unit Testing Framework - Getting Started Guide - Running Unit Tests - Version 2 Beta ", 2009-08 - Running Unit Tests.
  • Tellingmachine "Downloading historical weather station data using Advanced PowerShell functions", 2009-06 - Early Internet-of-Things ( IOT ) project.
• Installation by GitHub:
  1. Download the archive “PSUnit-master.zip” from GitHub to a local directory.
  2. Unzip the archive “PSUnit-master.zip”, so that the directory “PSUnit-master” is created.
  3. Copy the directory “PSUnit-master” to the installation directory. “PSUnit” is no module, so the installation directory can be placed at any location ( e.g. it may be “C:\Program Files\PSUnit” or in the PowerShell module directory ).
  4. Copy files “PSUnit-master\BuildProcessTemplates\Microsoft.PowerShell_profile.ps1” and “PSUnit-master\BuildProcessTemplates\Microsoft.PowerShellISE_profile.ps1” to the directory “C:\Users\Administrator\Documents\windowspowershell”, or modify existing files in that directory.
  5. Rename the installation directory “PSUnit-master” it to “PSUnit”.
  6. As “PSUnit” is no module, you must now add the full installation path of the directory to your system path PATH ( by “Settings / Control Panel / System / Advanced System Settings / Environment Variables / System Variables 'Path'” ).
  7. With the current version, the file “PSUnit.Exceptions.ps1” is missing. Please create a dummy file ( e.g. a file with a comment ”#” only ) in the installation directory.
  8. Add to “Microsoft.PowerShellISE_profile.ps1” ( e.g. <user> = “Administrator” ):

Set-ExecutionPolicy Unrestricted
Set-ExecutionPolicy Bypass
.  C:\Users\Administrator\Documents\windowspowershell\profile.ps1
. PSUnit.ISE.ps1

• Preparation for operation:
  • Create batch files to execute the test runner “PSUnit.Run.ps1” ( which is by installation in your system path PATH ), e.g. batch file “run_darth.bat” with the script instructions
    • “powershell PSUnit.Run.ps1 .\Darth-Enumerator.Test.ps1”.
• Logging:
  • Logging files ( e.g. “PSUnitTestReport_Darth-Enumerator.Test.ps1_2015-06-03-19-45-03_T43P37F6S0.html” ) are created by default in the installation directory , i.e. not in the user directory ( e.g. “C:\users\<username>\PSUnitTest” ).

• GitHub "lidingshan/PSUnit".
• BitBucket "Dingshan Li (lidingshan)" (?).
• Twitter "Mike Li, @lidingshan", SlideShare "Mike Li" (?).
• Installation by GitHub:
  1. Download the archive “PSUnit-master.zip” from GitHub to a local directory.
  2. Unzip the archive “PSUnit-master.zip”, so that the directory “Pester-master” is created.
  3. Copy the directory “PSUnit-master” to the PowerShell module directory.
  4. Rename the directory “PSUnit-master” it to “PSUnit”.
• Right now, PSUnit cannot handle the comments in test scripts. So even if one function has been commented, like ”# function test_add()”, PSUnit will still run this test.

• GitHub "lerwine/PSUnitTesting".
• The Erwine Family Website.
• Installation by GitHub:
  1. Download the archive “PSUnitTesting-master.zip” from GitHub to a local directory.
  2. Unzip the archive “PSUnitTesting-master.zip”, so that the directory “Pester-master” is created.
  3. Copy the directory “PSUnitTesting-master” to the PowerShell module directory.
  4. Rename the directory “PSUnitTesting-master” it to “Pester”.
• Preparation for operation:
  • Create batch files to execute the test runner “ModuleTests.ps1”, e.g. for Windows
    • A batch file “RunTests.bat” with the script instructions
      • “powershell -file ”.\Code\ModuleTests.ps1” %1 -ExecutionPolicy Bypass”.
    • You must call the application by “RunTests.bat MyScript.ps1” to test your script “MyTest.ps1”.
    • Unfortunately, no test scripts are provided... .

• Microsoft MSDN Magazine "Lightweight Testing with Windows PowerShell" - Download of Windows application “TestRun2007_05.exe”.
• Microsoft MSDN Magazine "UI Automation with Windows PowerShell" - Download of Windows application “TestRun2007_12.exe”.
• Microsoft MSDN Magazine "Web UI Automation with Windows PowerShell" - Download of Windows application “TestRun2008_03.exe”.
• Microsoft MSDN Magazine "Test Run: Web UI Automation with Windows PowerShell", 2008-04-04.

• The training requires that You must copy a sample web application to your IIS web server. On Win8.1, the root file system is at “C:\inetpub\wwwroot”.
  1. The sample scripts expects the website at “http://localhost/MiniCalc/”, while the subdirectory of the installation archiver is named “MiniCalcWeb”.
  2. So please rename “MiniCalcWeb” to “MiniCalc”, so that the web application is situated at “C:\inetpub\wwwroot\MiniCalc”.
• The sample web application configuration file “Web.config” must be upgraded for use with the IIS of Win8.1 .
  1. Error message “Duplicate 'system.web.extensions/scripting/scriptResourceHandler' section”.
     • StackOverflow "IIS7 deployment - duplicate 'system.web.extensions/scripting/scriptResourceHandler' sectionIIS7 deployment - duplicate 'system.web.extensions/scripting/scriptResourceHandler' section" - “Another quick fix is to have the application pool set to 2.0”.
     • “Internet Information Services (IIS) Manager”: “Connections - Application Pools: 'Default' / Basic Settings / .NET CLR Version: '.NET CLR Version v2.050727'”.
  2. Error message “Config Error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=“Deny”), or set explicitly by a location tag with overrideMode='Deny' or the legacy allowOverride='false'”.
     • StackOverflow "IIS - this configuration section cannot be used at this path (configuration locking?)" - “Built a fresh Windows Server 2012 and sure enough, forgot to add Application Development under Web Server”.
     • “Settings / Control Panel / Programs and Features / Turn Windows features on or off: / Internet Information Services / World Wide Web Services / Application Development Features: [x] ASP, [x] ASP.NET 3.5, [x] ASP.NET 4.5”.
  3. Error message “Configuration Error ”<authentication mode=“Windows” />” + It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level”.
     • Microsoft IIS Forums "Configuration Error "<authentication mode="Windows" />" + It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level".
     • Microsoft ASP.NET Forums "Configration error at authentication mode=Windows RSS" - “Comment it then the error go away. It is incredible”.

• Pluralsight blog Where devs, IT admins & creative pros go for news, tips, videos and more "Test PowerShell with WhatIf".